-
Notifications
You must be signed in to change notification settings - Fork 15
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
MRF Version and Validator Version Mismatch #121
Comments
blakehice4
changed the title
MRF Version mismatch
MRF Version and Validator version mismatch
Nov 5, 2024
blakehice4
changed the title
MRF Version and Validator version mismatch
MRF Version and Validator Version Mismatch
Nov 5, 2024
looks like the version is pulled from git tags. i'm thinking in here we can add some logic to include versions without the v?
|
blakehice4
added a commit
to blakehice4/price-transparency-guide-validator
that referenced
this issue
Nov 5, 2024
blakehice4
added a commit
to blakehice4/price-transparency-guide-validator
that referenced
this issue
Nov 5, 2024
was a little more complex than i thought. i think i have a decent start here |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I believe there was an update done to automatically pull version from the MRF and use that in the validator tool.
This logic does not handle the use case where the MRF version does not have a v prefix.
Can a modification be made to automatically handle versions without the v prefix like what is shown here https://github.com/CMSgov/price-transparency-guide/blob/0374c479ed146aa3c62e6460012b37fcaa3e5288/examples/in-network-rates/in-network-rates-fee-for-service-single-plan-sample.json#L9
The text was updated successfully, but these errors were encountered: