Interactivity API: Roadmap #52904
Replies: 3 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.
0 replies
-
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.
0 replies
-
I've closed the Core blocks and new |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
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
template
during thetoVdom
phase (required fordata-wp-each
)wp-each
directive #57859useInit
anduseWatch
hookswp-run
directive anduseInit
&useWatch
hooks #57805data-wp-text
, only stringswp-text
#57879state
and renameprops
toattributes
ingetElement()
#57974withScope
and add support for async functions (generators)withScope()
and allow to use it with asynchronous operations. #58013init
Directives
components (or top component) avoids unnecessary rerendersdata-wp-interactive
withdata-wp-ignore
to make sure that an isolated block doesn't accidentally close a parent blockdata-wp-style
directive (runtime)wp-style
directive #52645data-wp-interactive="namespace"
data-wp-interactive
#58743data-wp-key
that is linked to Preact'skey
:data-wp-key
directive #53844data-wp-run
directivewp-run
directive anduseInit
&useWatch
hooks #57805data-wp-on-window
anddata-wp-on-document
directiveswp-data-on-window
andwp-data-on-document
directives #57931data-wp-each
wp-each
directive #57859afterLoad
callbacks tostore()
function woocommerce/woocommerce-blocks#10338afterLoad
callbacks tostore
calls #53363data-wp-bind
during hydrationrole
logic in our codebaserole
attribute when set tonull
indata-wp-bind
#54608 (comment)data-wp-bind
data-wp-slot
anddata-wp-fill
directivesdata-wp-component
)data-wp-body
directive or a slot in the bodydata-wp-show
directivewp-show
attribute directive processor block-interactivity-experiments#141data-wp-dangerous-html
taking into account security (no scripts?)data-wp-bind
ordata-wp-text
, when the path is fromstate
orcontext
data-wp-interactive='{ "namespace": "..." }'
wp_initial_state()
#57556wp_interactivity_process_directives()
data-wp-each
data-wp-each
#58498data-wp-context
on PHPdata-wp-bind
during SSRwp_store
aswp_interactivity_state
wp_initial_state()
#57556navigate
calls #54201core/router
store and move thenavigate
andprefecth
actions there@wordpress/interactivity-router
module #57924core/router
store in@wordpress/interactivity/router
@wordpress/interactivity-router
module #57924state.url
in thecore/router
storeconfig['core/router'].regionNavigation = false
timeout
option tonavigate()
#54474dom
option tonavigate
to accept a parsed DOM.clientNavigation
andinteractive
to block supports metadata.block supports
forclientNavigation
andinteractive
properties onblock.json
schema. #58132data-wp-link
utm*
) for the client page cachepreact/debug
to developmentgetElement
in productionBeta Was this translation helpful? Give feedback.
All reactions