Interactivity API: Roadmap #52904
Replies: 5 comments
-
|
I've closed the previous Tracking Issue as completed: And opened a new one for the next iteration: |
Beta Was this translation helpful? Give feedback.
-
|
I've opened a new Tracking Issue to track the ongoing efforts to improve the way we process directives in the server: |
Beta Was this translation helpful? Give feedback.
-
|
I've closed the Core blocks and new |
Beta Was this translation helpful? Give feedback.
-
|
This was the tracking issue related to the changes made in WordPress 6.6. |
Beta Was this translation helpful? Give feedback.
-
|
This is the tracking issue to keep the progress of the planned changes for WordPress 6.7. |
Beta Was this translation helpful? Give feedback.
-
This is the list of tasks that we currently have in mind for the Interactivity API. This list is being updated as we progress and learn more about the needs of this initiative.
We'll keep this list updated, but we will use Tracking Issues to track who is doing what, which PRs are opened, merged and so on. We'll add a comment here each time we open a new Tracking Issue so anyone interested in the development can subscribe to it, and we'll update the list to reflect what has been completed and add links to the relevant issues and PRs. So please subscribe to this discussion if you want to follow the development of the Interactivity API.
If you have ideas or suggestions, don't comment here!! Please open a separate discussion in the Interactivity API category instead.
Current Tracking Issue
templateduring thetoVdomphase (required fordata-wp-each)wp-eachdirective #57859useInitanduseWatchhookswp-rundirective anduseInit&useWatchhooks #57805data-wp-text, only stringswp-text#57879stateand renamepropstoattributesingetElement()#57974withScopeand add support for async functions (generators)withScope()and allow to use it with asynchronous operations. #58013initDirectivescomponents (or top component) avoids unnecessary rerendersdata-wp-interactivewithdata-wp-ignoreto make sure that an isolated block doesn't accidentally close a parent blockattributesis handleddata-wp-styledirective (runtime)wp-styledirective #52645data-wp-interactive="namespace"data-wp-interactive#58743data-wp-keythat is linked to Preact'skey:data-wp-keydirective #53844data-wp-rundirectivewp-rundirective anduseInit&useWatchhooks #57805data-wp-on-windowanddata-wp-on-documentdirectiveswp-data-on-windowandwp-data-on-documentdirectives #57931data-wp-eachwp-eachdirective #57859afterLoadcallbacks tostore()function woocommerce/woocommerce-blocks#10338afterLoadcallbacks tostorecalls #53363data-wp-bindduring hydrationrolelogic in our codebaseroleattribute when set tonullindata-wp-bind#54608 (comment)data-wp-binddata-wp-slotanddata-wp-filldirectivesdata-wp-client-only-component)data-wp-showdirectivewp-showattribute directive processor block-interactivity-experiments#141data-wp-dangerous-htmltaking into account security (no scripts?)data-wp-bindordata-wp-text, when the path is fromstateorcontextdata-wp-eachrecursivelydata-wp-interactive='{ "namespace": "..." }'wp_initial_state()#57556wp_interactivity_process_directives()data-wp-eachdata-wp-each#58498data-wp-contexton PHPdata-wp-bindduring SSRwp_storeaswp_interactivity_statewp_initial_state()#57556navigatecalls #54201core/routerstore and move thenavigateandprefecthactions there@wordpress/interactivity-routermodule #57924core/routerstore in@wordpress/interactivity/router@wordpress/interactivity-routermodule #57924state.urlin thecore/routerstoreconfig['core/router'].regionNavigation = falsetimeoutoption tonavigate()#54474domoption tonavigateto accept a parsed DOM.clientNavigationandinteractiveto block supports metadata.block supportsforclientNavigationandinteractiveproperties onblock.jsonschema. #58132data-wp-linkutm*) for the client page cachepreact/debugto developmentpreact/debugwhenSCRIPT_DEBUGis enabled #60514getElementin productionBeta Was this translation helpful? Give feedback.
All reactions