Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Relevance of repeat instances is evaluated in unexpected way #634

Open
lognaturel opened this issue May 21, 2021 · 1 comment
Open

Relevance of repeat instances is evaluated in unexpected way #634

lognaturel opened this issue May 21, 2021 · 1 comment

Comments

@lognaturel
Copy link
Member

Software versions

JavaRosa v3.1.0

Problem description

Relevance of repeat instances is evaluated in unexpected way

Steps to reproduce the problem

Start with this form. Instead of the nested veg group, put the relevance condition on the repeat itself. If you try to select any choice but the first one, no repeat instance exists. If you first select 'Beans' (the first choice), then the form works as expected with the first two choices. If you select the first two choices, then the form works with the first three choices, etc.

Expected behavior

I think relevance should be computed independently on every repeat instance?

@lognaturel
Copy link
Member Author

It's like the repeat instances have to be explicitly traversed to be created before their relevance is evaluated or something. Consider this variation which adds a count-selected(${tf_local_veg}) = 0 case to the relevance condition. In Collect, if you go to the hierarchy view and see the repeat there, then the form works as expected. Or if you jump to swipe through repeat instances without selecting vegetables, that also works. However, linear traversal doesn't work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant