This repository has been archived by the owner on Nov 29, 2023. It is now read-only.
[WIP] Fix nested repeats with relevance #806
Closed
Conversation
This file contains 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
eyelidlessness
force-pushed
the
fix/issue-804-nested-repeat-relevance
branch
from
fe84607 to
bc5bc5f
Compare
This is a targeted fix for one user, addressing a case where relevance on a nested/grouped repeat only works for the first top-level repeat. It causes a test failure for another use case, which provides helpful testing context and sort of hints at a likely direction for a more general fix.
eyelidlessness
force-pushed
the
fix/issue-804-nested-repeat-relevance
branch
from
bc5bc5f to
31993ef
Compare
eyelidlessness
added a commit
to eyelidlessness/enketo-express
that referenced
this pull request
Aug 27, 2021
Currently sets dependency to branch for enketo/enketo-core#806
This was referenced Aug 27, 2021
|
Replaced by #807 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This is, temporarily, a targeted fix for one user, addressing a case where relevance on a nested/grouped repeat only works for the first top-level repeat. It causes a test failure for another use case, which provides helpful testing context and sort of hints at a likely direction for a more general fix.