-
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
Introduce withSyncEvent
action wrapper utility and proxy event
object whenever it is not used
#68097
Open
felixarntz
wants to merge
10
commits into
trunk
Choose a base branch
from
add/64944-with-sync-event
base: trunk
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+288
−81
Open
Introduce withSyncEvent
action wrapper utility and proxy event
object whenever it is not used
#68097
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
60448fe
Implement withSyncEvent action wrapper utility.
felixarntz dba93ec
Prepare Interactivity API infrastructure for awareness of action prio…
felixarntz 5201460
Merge branch 'trunk' into add/64944-with-sync-event
felixarntz dad7083
Proxy event object when withSyncEvent() is not used.
felixarntz 524bf72
Merge branch 'trunk' into add/64944-with-sync-event
felixarntz 21e51be
Ensure generator functions using withSyncEvent() are wrapped correctl…
felixarntz a582f01
Update Interactivity API documentation to reference withSyncEvent().
felixarntz 5d68fcb
Use withSyncEvent() in all built-in actions that require it.
felixarntz d5de596
Merge branch 'trunk' into add/64944-with-sync-event
felixarntz 621a9c9
Minor fixes for withSyncEvent docs.
felixarntz File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -873,6 +873,8 @@ const { state } = store( 'myPlugin', { | |
} ); | ||
``` | ||
|
||
You may want to add multiple such `yield` points in your action if it is doing a lot of work. | ||
|
||
As mentioned above with [`wp-on`](#wp-on), [`wp-on-window`](#wp-on-window), and [`wp-on-document`](#wp-on-document), an async action should be used whenever the `async` versions of the aforementioned directives cannot be used due to the action requiring synchronous access to the `event` object. Synchronous access is required whenever the action needs to call `event.preventDefault()`, `event.stopPropagation()`, or `event.stopImmediatePropagation()`. To ensure that the action code does not contribute to a long task, you may manually yield to the main thread after calling the synchronous event API. For example: | ||
|
||
```js | ||
|
@@ -885,16 +887,17 @@ function splitTask() { | |
|
||
store( 'myPlugin', { | ||
actions: { | ||
handleClick: function* ( event ) { | ||
handleClick: withSyncEvent( function* ( event ) { | ||
event.preventDefault(); | ||
yield splitTask(); | ||
doTheWork(); | ||
}, | ||
} ), | ||
}, | ||
} ); | ||
``` | ||
|
||
You may want to add multiple such `yield` points in your action if it is doing a lot of work. | ||
You may notice the use of the [`withSyncEvent()`](#withsyncevent) utility function in this example. This is necessary due to an ongoing effort to handle store actions asynchronously by default, unless they require synchronous event access. Otherwise a deprecation warning will be triggered, and in a future release the behavior will change accordingly. | ||
|
||
|
||
#### Side Effects | ||
|
||
|
@@ -1253,6 +1256,43 @@ store( 'mySliderPlugin', { | |
} ); | ||
``` | ||
|
||
### withSyncEvent() | ||
|
||
Actions that require synchronous access to the `event` object need to use the `withSyncEvent()` function to wrap their handler callback. This is necessary due to an ongoing effort to handle store actions asynchronously by default, unless they require synchronous event access. Therefore, as of Gutenberg `TODO: Add release number here!` / WordPress 6.8 all actions that require synchronous event access need to use the `withSyncEvent()` utility wrapper function. Otherwise a deprecation warning will be triggered, and in a future release the behavior will change accordingly. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Note: The |
||
|
||
Only very specific event methods and properties require synchronous access, so it is advised to only use `withSyncEvent()` when necessary. The following event methods and properties require synchronous access: | ||
|
||
* `event.currentTarget` | ||
* `event.preventDefault()` | ||
* `event.stopImmediatePropagation()` | ||
* `event.stopPropagation()` | ||
|
||
Here is an example, where one action requires synchronous event access while the other actions do not: | ||
|
||
```js | ||
// store | ||
import { store, withSyncEvent } from '@wordpress/interactivity'; | ||
|
||
store( 'myPlugin', { | ||
actions: { | ||
// `event.preventDefault()` requires synchronous event access. | ||
preventNavigation: withSyncEvent( ( event ) => { | ||
event.preventDefault(); | ||
} ), | ||
|
||
// `event.target` does not require synchronous event access. | ||
logTarget: ( event ) => { | ||
console.log( 'event target => ', event.target ); | ||
}, | ||
|
||
// Not using `event` at all does not require synchronous event access. | ||
logSomething: () => { | ||
console.log( 'something' ); | ||
}, | ||
}, | ||
} ); | ||
``` | ||
|
||
## Server functions | ||
|
||
The Interactivity API comes with handy functions that allow you to initialize and reference configuration options on the server. This is necessary to feed the initial data that the Server Directive Processing will use to modify the HTML markup before it's send to the browser. It is also a great way to leverage many of WordPress's APIs, like nonces, AJAX, and translations. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
11 changes: 8 additions & 3 deletions
11
packages/e2e-tests/plugins/interactive-blocks/get-server-context/view.js
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
11 changes: 8 additions & 3 deletions
11
packages/e2e-tests/plugins/interactive-blocks/get-server-state/view.js
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
6 changes: 3 additions & 3 deletions
6
packages/e2e-tests/plugins/interactive-blocks/router-styles-wrapper/view.js
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,20 +1,20 @@ | ||
/** | ||
* WordPress dependencies | ||
*/ | ||
import { store } from '@wordpress/interactivity'; | ||
import { store, withSyncEvent } from '@wordpress/interactivity'; | ||
|
||
const { state } = store( 'test/router-styles', { | ||
state: { | ||
clientSideNavigation: false, | ||
}, | ||
actions: { | ||
*navigate( e ) { | ||
navigate: withSyncEvent( function* ( e ) { | ||
e.preventDefault(); | ||
const { actions } = yield import( | ||
'@wordpress/interactivity-router' | ||
); | ||
yield actions.navigate( e.target.href ); | ||
state.clientSideNavigation = true; | ||
}, | ||
} ), | ||
}, | ||
} ); |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.