Docs: Update @wordpress/data README with API changes#27180
Merged
Conversation
gziolo
commented
Nov 22, 2020
|
Size Change: 0 B Total Size: 1.19 MB ℹ️ View Unchanged
|
a771765 to
5f3a817
Compare
141cf47 to
a4a2c55
Compare
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
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.
Description
Follow up for #26655 and #27061 that introduce API changes to
@wordpress/datapackage.This PR adds a section in the CHANGELOG file with deprecations for
registerStoreandregisterGenericStorefunctions. Both functions are marked as deprecated in JSDoc comments. I don't think we are ready to add deprecation warnings in the code until we update usage in Gutenberg but that might take some time.Changes
The best way to see all important changes in this PR is with this view:
https://github.com/WordPress/gutenberg/pull/27180/files?diff=unified&w=1