Currently, constraint violation messages are not returned from procedural constraints. To support this in the backend, the following needs to be done:
- add an
Optional<String> message field to the record gov.nasa.jpl.aerie.constraints.model.Violation.
- update the method
fromProceduralViolations gov.nasa.jpl.aerie.constraints.model.Violation to extract the message from the procedural Violation and put it in this new field
- update
violationP in gov.nasa.jpl.aerie.constraints.json.ConstraintParsers to include this new optional message field
Currently, constraint violation messages are not returned from procedural constraints. To support this in the backend, the following needs to be done:
Optional<String> messagefield to the recordgov.nasa.jpl.aerie.constraints.model.Violation.fromProceduralViolationsgov.nasa.jpl.aerie.constraints.model.Violationto extract the message from the procedural Violation and put it in this new fieldviolationPingov.nasa.jpl.aerie.constraints.json.ConstraintParsersto include this new optionalmessagefield