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

Value Set Name Not Showing For Related Artifact #54

Open
JSRankins opened this issue Jan 12, 2024 · 2 comments
Open

Value Set Name Not Showing For Related Artifact #54

JSRankins opened this issue Jan 12, 2024 · 2 comments
Milestone

Comments

@JSRankins
Copy link

The value set name (or local identifier) is what is used to reference the value set in a CQL expression. This is what appears in the logic definitions in the human readable. However, the related artifact in the human readable is only showing the canonical URL without the local identifier, so it is not possible to match the related artifact to the value set in use in the expression without opening the CQL library. Please update.

@JSRankins JSRankins changed the title Value Set Name Not Showing For Related Artifiact Value Set Name Not Showing For Related Artifact Feb 18, 2024
@juliet-rubini juliet-rubini added this to the Path to v0.4.2 milestone May 9, 2024
@echicoine-icf
Copy link

Seems like no matter what I try, the moment the value set url is referenced the publisher automatically attempts to turn that into a display name and url combo, and for some reason sometimes the url does not do this (possibly because the fetch for that info failed?)

Example:

image

@brynrhodes
Copy link
Member

Hmm.... that definitely looks like something the publisher is automatically applying, and I'm not sure there's currently a way around that. Might need a question in the IG Creation thread to ask whether there is a way to disable that behavior, since we're doing it ourselves already in the template?

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

4 participants