TMSS-917: primary subtask

It proved quite difficult to have the "constraint" of only one primary subtask per parent task_blueprint.

In order to achieve that I had to rewrite TMSS-568 such that the parallel calibrator and target LBA subtask are now in one single parent TaskBlueprint, but defined in two subsections in the json schema. That rewrite was much bigger than the "primary" subtask stuff.

Reintroduced the not-null constraint on the parent TaskBlueprint for the Subtask.

Also had to adapt many tests for the new restrictions.

All in all, we now have a much more strict but usable model.

Closes TMSS-917

added 4 commits

• 5f324d14 - TMSS-917: no definitions referenced_schema, make empty default
• 35262aa3 - TMSS-917: raise more specific json decode error
• 4c72a475 - TMSS-917: refactored the parallel LBA calibrator and target observations into...
• 877de1a3 - TMSS-917: reverted to a single parent TaskBlueprint for a Subtask.

Compare with previous version

marked this merge request as draft

added 1 commit

• c479d556 - TMSS-917: adapted and fixed various tests now that we reverted to a single...

Compare with previous version

added 1 commit

• 7210bec8 - TMSS-917: adapted and fixed various tests now that we reverted to a single...

Compare with previous version

added 1 commit

• 75cc671a - TMSS-917: adapted and fixed various tests now that we reverted to a single...

Compare with previous version

added 1 commit

• d05db5bd - TMSS-917: adapted and fixed various tests now that we reverted to a single...

Compare with previous version

added 1 commit

• 776f350e - TMSS-917: adapted and fixed various tests now that we reverted to a single...

Compare with previous version

added 1 commit

• 7ecb974f - TMSS-917: now that we reverted to a single parent TaskBlueprint for a Subtask...

Compare with previous version

added 83 commits

• 7ecb974f...7c5d4899 - 82 commits from branch master
• efd221a5 - Merge branch 'master' into TMSS-917

Compare with previous version

added 1 commit

• f08b2a62 - TMSS-917: ensure that each parent task_blueprint has exactly one primary child...

Compare with previous version

added 1 commit

• df547814 - TMSS-917: made parent TaskBlueprint mandatory for Subtasks. Adapted tests accordingly.

Compare with previous version

added 2 commits

• b607cc62 - TMSS-917: fixed tests
• e4fd2bd3 - TMSS-917: fixed tests

Compare with previous version

changed the description

marked this merge request as ready

Code looks good. Had to read the triple get one liner a couple of times though.

A question that I have before we can merge. Would we break the front-end with this merge?

Would we break the front-end with this merge?

I don't think so. The frontend hardly uses subtasks, and it's the subtask reference to its parent task_blueprint that changed from ManyToMany to a plain ForeighnKey. I scanned the frontend code for occurrences of the property 'task_blueprints' but it's only used on scheduling_unit_blueprint instances, never on subtasks.

Ok I will merge it then.

merged

mentioned in commit 94ecce36