js: denextify #1027
Merged
js: denextify #1027
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
11d399c to
433d80d
Compare
For a long time we have had two APIs for the JavaScript @automerge/automerge package. The "stable" API and the "next" API. The "next" API had some significant differences from the stable API but we didn't want to make a breaking change in the API until we were confident of these differences. The most significant difference being the use of `string` to represent text rather than a the `Text` class in the "stable" API. We're now very sure of the "next" API and the complexity of maintaining two APIs is no longer worth it, we're going to do a major version bump to release the new compressed memory OpSet, so removing the old "stable" API seems like a good thing to do at the same time.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For a long time we have had two APIs for the JavaScript @automerge/automerge package. The "stable" API and the "next" API. The "next" API had some significant differences from the stable API but we didn't want to make a breaking change in the API until we were confident of these differences. The most significant difference being the use of
stringto represent text rather than a theTextclass in the "stable" API. We're now very sure of the "next" API and the complexity of maintaining two APIs is no longer worth it, we're going to do a major version bump to release the new compressed memory OpSet, so removing the old "stable" API seems like a good thing to do at the same time.