Join GitHub today
Data Module: Support controls in resolvers #9507
This PR tweaks the data module to allow extended usage of the controls API in resolvers. To achieve that it does:
fulfill is fine,
rungen is fine, promises returned from dispatch is fine.
I'm not really digging our mixed consideration of resolvers. Is a resolver one of the proper concepts of the registry? If so, we're losing optimizations by wrapping selectors in
registerResolvers. If not, we need to stop referencing
resolvers in the plugins, in
registerSelectors, and in the registry
Ok, this PR now is in a much better shape. I think it's getting ready to
I wanted to deprecated the async-generator middleware/plugin but thought I would first wait for us to refactor the current async generators we have in Gutenberg to use controls and do that right after.