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.
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
Fish With Version #1275
Fish With Version #1275
Changes from 7 commits
900e6fc
19ab78e
4e871d3
ff23abe
4780f60
3e8be48
2966e53
11d0cfa
9668cdc
70e31fc
0d0852d
18b8ba8
3a9f3e9
858c75d
0b7ae4d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see that this change makes it more consistent w/ the approach we take for value sets below -- so that's good.
I also see that if there is a version, we drop the version when there's a match but keep it when there isn't (value sets below does the same thing). I think this is one of those places where we want to keep the version when there is a match. I think we had decided, however, that these kinds of changes aren't necessarily in scope for this PR and can be deferred to another PR if we want.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now that I have your nifty regex replace in my back pocket, I don't mind doing it here. But I can also hold off for a separate PR if that's preferred.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, wait, now I'm not sure if I agree we should keep the version. The version the author specified gets added to the
composeElement.version
regardless of if we find a match on line 63. And because thefoundSystem
variable does a finalsplit('|')
and then onlyfoundSystem[0]
is used later, the version is always spliced off and never added tocomposeElement.system
. So do we want to include the|version
on thesystem
property, as well as on theversion
property?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, dang. You're right! For whatever reason,
ValueSet.compose.include
splits the version off into its own element. And thesystem
element isuri
notcanonical
. So, yep, we definitely do not want to attach the|version
. Good call!