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.

Sign up for GitHub

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

Jump to bottom

Version Handling #106

Open
johnharris85 opened this issue Aug 12, 2018 · 0 comments
Open

Version Handling #106

johnharris85 opened this issue Aug 12, 2018 · 0 comments
Labels
DIVER Overall Project enhancement New feature or request

Comments

@johnharris85
Copy link
Collaborator

Need a strategy around version handling. Because some of the features / APIs we're working with / exposing are not part of the official API we can't rely on API Version and sometimes have to track on UCP Version (HRM / Interlock is an example of this). Mind-dump:

  • Track feature / endpoint mapping somewhere
  • Ensure we track UCP version and API version in sessions
  • Different client per version? (probably not as the API doesn't diverge that much)
  • Different feature handling per version (probably easier to begin with but can get messy)
  • Etc...
@johnharris85 johnharris85 added enhancement New feature or request DIVER Overall Project labels Aug 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
DIVER Overall Project enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@johnharris85