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.

Sign up for GitHub

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

Jump to bottom

Implementation loop cursor not properly reset for multiple occurrences #223

Closed
MikeEdgar opened this issue Nov 27, 2021 · 0 comments · Fixed by #224
Closed

Implementation loop cursor not properly reset for multiple occurrences #223

MikeEdgar opened this issue Nov 27, 2021 · 0 comments · Fixed by #224
Assignees
@MikeEdgar
Labels
bug
Milestone
v1.18.2

Comments

@MikeEdgar
Copy link
Member

When reading an input stream containing multiple occurrences of an implementation loop not in the exact order specified in the implementation schema, occurrences fail to match earlier discriminator values once they are passed the first time.

E.g. 837 implementation loops received:

  • 2000A
  • 2000B
  • 2000C
  • 2000A
  • 2000B
  • 2000C

Would be incorrectly processed as:

  • 2000A
  • 2000B
  • 2000C
  • 2000C
  • 2000C
  • 2000C
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@MikeEdgar MikeEdgar

Labels
bug
Projects
None yet
Milestone
v1.18.2
Development

Successfully merging a pull request may close this issue.

Allow implementation nodes to occur/reoccur in any order in the input xlate/staedi
1 participant
@MikeEdgar