feat: qcu options based on loop response#1368
Merged
Conversation
nsenave
reviewed
Feb 20, 2026
Contributor
nsenave
left a comment
There was a problem hiding this comment.
Le fonctionnel a l'air bon, mais du refacto à faire à certains endroits
laurentC35
reviewed
Feb 20, 2026
laurentC35
requested changes
Feb 20, 2026
Contributor
laurentC35
left a comment
There was a problem hiding this comment.
L'expression doit être finalement false, cf mon commentaire
nsenave
reviewed
Feb 24, 2026
…hub.com/InseeFr/Eno into feat/qcu-options-based-on-loop-response
…hub.com/InseeFr/Eno into feat/qcu-options-based-on-loop-response
|
👋 Image 3.61.1-0b10e8c deployed on docker hub |
|
laurentC35
approved these changes
Mar 6, 2026
nsenave
approved these changes
Mar 9, 2026
nsenave
pushed a commit
that referenced
this pull request
Mar 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



The bindingDependencies of the optionFilter are correctly set on the Lunatic side to support dynamic recalculation.
At this stage, only the cleaning linked to optionSource is implemented, as it is essential to ensure response consistency.
Conditional cleaning based on the optionFilter did not exist previously and has not yet been implemented; it could be added later using these bindings.
The choice of ConditionFilterType in the process was made precisely to allow this, as it facilitates the proper handling of bindingDependencies.