-
Notifications
You must be signed in to change notification settings - Fork 2k
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
SDK: Try wp.data with calypso state tree #26838
Commits on Sep 6, 2018
-
state: Try wp.data with calypso state tree
This adds a wp.data plugin that uses the existing calypso state tree but pulls in selectors as a first step to being cross-platform.
Configuration menu - View commit details
-
Copy full SHA for 4e0f7a6 - Browse repository at this point
Copy the full SHA 4e0f7a6View commit details -
state: Action handling for wp.data calypso plugin
This adds action dispatch handling for the wp.data calypso plugin to allow existing Calypso actions to be dispatched against the Calypso store.
Configuration menu - View commit details
-
Copy full SHA for 4befbc1 - Browse repository at this point
Copy the full SHA 4befbc1View commit details -
state: wp.data adapter adjustments
This addresses a couple of PR comments about some optimization and additional commenting.
Configuration menu - View commit details
-
Copy full SHA for 1388482 - Browse repository at this point
Copy the full SHA 1388482View commit details -
state: Add WP Data Provider to ReduxWrappedLayout
This adds the data provider to ReduxWrappedLayout in addition to RootChild
Configuration menu - View commit details
-
Copy full SHA for bcc4b32 - Browse repository at this point
Copy the full SHA bcc4b32View commit details -
wp-data: Put preferences in
calypso/preferences
This moves the preferences selectors/actions from a `calypso` wp.data store to a `calypso/preferences` wp.data store, for the purpose of separating out these stores and organizing them better. This also lays the groundwork for separating out the monolithic state tree in calypso today.
Configuration menu - View commit details
-
Copy full SHA for 17b8bda - Browse repository at this point
Copy the full SHA 17b8bdaView commit details -
State: Use more general-purpose wp.data plugins.
This creates a `custom-store-plugin` which is more general-purpose than the previous `calypso-registry-plugin`. It allows any pre-existing redux store to be used for a given wp.data store instead of wp.data creating one itself. This allows for two things: 1. Stores can use enhancers and middleware, which is not possible in the default wp.data configuration. 2. wp.data stores can share redux stores. Note: This also creates an `internals-plugin`, which is necessary to avoid the reimplementing of internals within the `calypso-registry-plugin`. The `use` function of the `internals-plugin` will be submitted as a PR to core Gutenberg as well so perhaps it will not be necessary for long.
Configuration menu - View commit details
-
Copy full SHA for d7324b4 - Browse repository at this point
Copy the full SHA d7324b4View commit details -
wp-data: internals-plugin, mutate registry in use
This switches the code back to the way it works in @wordpress/data because it's necessary to chain plugins.
Configuration menu - View commit details
-
Copy full SHA for 6d8a6cf - Browse repository at this point
Copy the full SHA 6d8a6cfView commit details -
wp-data: custom-store-plugin, adjust subscribe
This adjusts the plugin to not subscribe to the same custom store more than once when it's passed in as a custom store for more than one wp.data registerStore call.
Configuration menu - View commit details
-
Copy full SHA for 90b204b - Browse repository at this point
Copy the full SHA 90b204bView commit details -
This is to fix the CI errors on the PR that are complaining about the shrinkwrap not being in sync.
Configuration menu - View commit details
-
Copy full SHA for c5a4515 - Browse repository at this point
Copy the full SHA c5a4515View commit details