Skip to content

Migrate Configuration of Constraint Templates

🚀 Feature Request

Summary

Migrate the configuration of constraint templates in QPM from Java classes to YAML or JSON files. This change will make it easier to modify, manage, and document constraint templates within the main repository of Constrainify.

Problem to Solve / User Story

As a Constrainify maintainer, I want constraint templates to be defined in YAML or JSON in the main constrainify repository instead of Java classes in QPM so that I can easily modify and maintain them without changing the QPM code.

Proposed Solution

  • Extract existing constraint templates from Java classes.
  • Define them in YAML or JSON format, ensuring all necessary parameters are included.
  • Store the configuration files in the Constrainify repository.
  • Provide proper documentation for maintainers on how to update and use these templates.
  • Add validation to ensure structure.

Benefits

  • Simplifies the process of modifying constraint templates.
  • Reduces dependency on QPM and developers.

Possible Drawbacks

  • Need to ensure valid configurations.

Alternatives Considered

  • Using an external database for storing and managing constraint templates.