-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Data: enable thunks by default and remove the experimental flag #38853
Conversation
Size Change: -187 B (0%) Total Size: 1.15 MB
ℹ️ View Unchanged
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Excellent!
Fantastic! Great work, @jsnajdr leading all the efforts 👏 Could there be any issues with 3rd party stores used by plugins now that this is always enabled? I assume no, but it’s always conforming to see confirmation 😃 |
@gziolo theoretically there could a conflict with custom middlewares, especially ones handling thunks. If we want to maintain 100% backwards compatibility then thunks would have to remain opt-in. I wonder how much of a problem that actually is, though cc @jsnajdr |
I think such a conflict can't happen. First, |
At any rate we're bumping the |
The thunks API has been around for quite a long time (one year, since #27276) and all Gutenberg stores have been migrated to it. That means that the API is battle tested and stable, and we can graduate it from the experimental status to stable. This PR does that. Removes the
__experimentalUseThunks
flag for store config and enables the thunk middleware by default for all stores.