Replace echo missions with just using mission definitions - #2694
Conversation
|
🔔 Changes in database files detected 🔔 |
fe6fde7 to
1f606d3
Compare
d30604f to
54646fe
Compare
|
🔔 Migrations changes detected 🔔 |
3f72478 to
44d7719
Compare
8b2fe8a to
8563f5e
Compare
a0a7b1a to
0966d88
Compare
f24e72f to
28b6d5d
Compare
436a6c5 to
40f2fa5
Compare
56f6e00 to
a23a008
Compare
Added: wire
|
155a2d6 to
1766809
Compare
Wire AnalysisTypes from the per-run Inspection into the JSON contract ISAR expects on /schedule/start-mission, so SARA can read it from the resulting MQTT inspection-result payload. Flotilla AnalysisType enum values are mapped to the strings SARA recognises (fencilla, cloe, thermal-reading, co2). Null or empty input serialises as null, in which case SARA falls back to its file-extension default.
The AnalysisTypes field on MissionTask was added alongside the analysis-types model but was never populated when a TaskDefinition template was turned into a runtime MissionTask. The data was only copied onto the nested Inspection. This left MissionTask.AnalysisTypes silently empty for every scheduled mission, and meant the round-trip back through ToMissionTaskDefinition zeroed out the analysis types. Populate both fields from the same source so the model is internally consistent.
1766809 to
c9d03e1
Compare
|
/UpdateDatabase |
Things to do after merging this PR:
Ready for review checklist: