Add item ordering in record value mapper to allow ordering of activity/scheduling goal parameters

[adrienmaillard]

• Tickets addressed: Yet to be written
• Review: By commit
• Merge strategy: Merge (no squash)

Description

Metadata containing item order is now attached to every RecordValueMapper so it can be used by the UI to display parameters in the order it has been defined in the scheduling procedures.

Changes in the UI are on branch https://github.com/NASA-AMMOS/aerie-ui/tree/ordering-scheduling-goal-params

Verification

With tests in RecordValueMapperTests. I also performed an end to end test with the UI code and activities/procedural goals. For ordering at the top level, I could use procedural goals but because of issue https://github.com/NASA-AMMOS/aerie/issues/1737 that I have found while developing, I had to test the nested ordering with activity parameters on the bananation model.

Documentation

Docs about parameters of mission models/procedural goals and constraints will have to mention that the way of ordering parameters is to go through records and use the default record value mapper. Custom value mappers for records will not produce the ordering.

Future work

None.

[sonarqubecloud[bot]]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud