feat: add critical checkbox to the norm node, send it with the program, add test. #29
Reference in New Issue
Block a user
Delete Branch "feat/norm-critical-checkbox"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
ref: N25B-390
This is a merge to add the checkbox to the norm and send it as part of its data to the CB.
Checklist:
Note that this also means adding this part to the CB, which currently doesn't happen. Meaning the program can't be validated untill this change is also reflected on CB. (I will do this on a branch.)
You should probably check this by adding
critical: boolto line 16 inprogram.pyin the CB.assigned to @9828273
changed the description
requested review from @j.gerla
removed review request for @j.gerla
marked the checklist item Checking and unchecking works as completed
marked the checklist item The run program outputs the correct program, including the new critical boolean. as completed
marked the checklist item Tests pass (one test added for this behaviour) as completed
marked the checklist item Eslint passes as completed
changed this line in version 2 of the diff
added 1 commit
d5480f95- Apply 1 suggestion(s) to 1 file(s)Compare with previous version
resolved all threads
changed this line in version 3 of the diff
added 1 commit
62c81186- Apply 1 suggestion(s) to 1 file(s)Compare with previous version
marked the checklist item Added code makes sense. as completed
resolved all threads
approved this merge request
resolved all threads
approved this merge request
I think merging this should be awaited until the other branch in cb is added.
If you have a reason for merging right now you can explain and do so, but if not its just a risk that this might break dev for the whole program
left review comments
mentioned in commit
faaf67138d