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

add 'support_versions' endpoint #152

Closed
hunterowens opened this issue Oct 25, 2018 · 3 comments
Closed

add 'support_versions' endpoint #152

hunterowens opened this issue Oct 25, 2018 · 3 comments
Milestone

Comments

@hunterowens
Copy link
Collaborator

To each API, add a supported version for programmatic checking of supported versions. Related to #147

@hunterowens
Copy link
Collaborator Author

How to articulate this, IMO.

MDS, as a spec, supports 2 minor versions. (ie, 0.2 and 0.1 rn)

Cities, as part of their regulatory guidance, can require particular version #s. For example, SM may require latest while LA requires latest or latest -1.

Finally, implementations, of either provider or agency, support n versions. For example, company_x’s Provider implementation might support 0.1.1, 0.2.0 and 0.3.1 while LA’s agency implementation might support 0.3.0

@oderby
Copy link
Contributor

oderby commented Feb 1, 2019

@hunterowens after writing up #216, I'm not sure I see the reason/value in this. Can you elaborate on what solving this would enable?

@hunterowens hunterowens added this to the 0.3.0 milestone Feb 3, 2019
@hunterowens
Copy link
Collaborator Author

yeah, with #216, I feel like this might not be required.

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

2 participants