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

Add requirement to the spec that new fields should not break existing libraries #81

Open
mattheworiordan opened this issue Mar 2, 2017 · 1 comment
Open

Add requirement to the spec that new fields should not break existing libraries #81

mattheworiordan opened this issue Mar 2, 2017 · 1 comment

Comments

@mattheworiordan
Copy link
Member

mattheworiordan commented Mar 2, 2017 •
edited by ably-sync-bot
Loading

See ably/ably-dotnet#97 for context.

The client library specification should state that all enum / flags should accept new unknown values and all types can have new fields i.e. we reserve the right to add new fields to responses without worrying about breaking existing libraries.

┆Issue is synchronized with this Jira Task by Unito
@mattheworiordan mattheworiordan mentioned this issue Mar 28, 2018
Closed
@QuintinWillison QuintinWillison transferred this issue from ably/docs Oct 3, 2022
@sync-by-unito
Copy link

sync-by-unito bot commented Oct 17, 2022

➤ Automation for Jira commented:

The link to the corresponding Jira issue is https://ably.atlassian.net/browse/SDK-2827

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
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mattheworiordan @tbedford