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

fix: 🐛 Check that VR has accessors for natural types (#368) #369

Merged
merged 1 commit into from
Nov 2, 2023

Conversation

dmlambo
Copy link
Contributor

@dmlambo dmlambo commented Oct 25, 2023

When naturalizing a dataset, the ValueRepresentation class used to add accessors may be ambiguous if the tag has multiple VR types. In this case we fall back to no accessor. There are only a handful of tags that fall into this category, and currently only PN has an accessor.

Specifically, this fixes the plethora of errors in OHIF stating ValueRepresentation.js:262 Invalid vr type xs - using US

When naturalizing a dataset, the ValueRepresentation class used to add
accessors may be ambiguous if the tag has multiple VR types. In this
case we fall back to no accessor. There are only a handful of tags that
fall into this category, and currently only PN has an accessor.
@pieper pieper merged commit 0365ca1 into dcmjs-org:master Nov 2, 2023
Copy link

github-actions bot commented Nov 2, 2023

🎉 This PR is included in version 0.29.12 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

Successfully merging this pull request may close these issues.

3 participants