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

editorial error: double negation in § 4.4 Api versions: prevents [...] not to get broken #239

Open
jonassmedegaard opened this issue May 17, 2021 · 0 comments
Open

editorial error: double negation in § 4.4 Api versions: prevents [...] not to get broken #239

jonassmedegaard opened this issue May 17, 2021 · 0 comments

Comments

@jonassmedegaard
Copy link

§ 4.4 Api versions contains this:

It is common to provide a separate API address after a breaking changes update. This prevents current clients not to get broken as these may not support these changes.

Seems the purpose is to prevent breakage - i.e. that the "not" in second sentence of the paragraph should be removed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jonassmedegaard