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 for new read-write API. #13

Open
nihiliad opened this issue Jun 1, 2022 · 0 comments
Open

Add support for new read-write API. #13

nihiliad opened this issue Jun 1, 2022 · 0 comments

Comments

@nihiliad
Copy link
Member

nihiliad commented Jun 1, 2022

The fact the new API, unlike the old one, has no version numbers in its URLs, and may just be unversioned, will present a challenge. In case the new API, once it replaces the old one, uses the same version scheme, keep the validation and support for that version scheme. Our local validation of collection/version-number combinations is valuable because the Pure API's error messages are not very descriptive, e.g. "Requested service was not found, message was: HTTP 404 Not Found" Find a way to support the currently unversioned new API alongside the old one.

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

No branches or pull requests

1 participant