Improve frontend guideline (#23252)
If an event listener must be `async`, the `e.preventDefault()` should be before any `await`, it's recommended to put it at the beginning of the function.
This commit is contained in:
parent
294124d129
commit
0a9a3c2a6d
1 changed files with 3 additions and 0 deletions
|
@ -83,6 +83,9 @@ It's not recommended to use `async` event listeners, which may lead to problems.
|
||||||
The reason is that the code after await is executed outside the event dispatch.
|
The reason is that the code after await is executed outside the event dispatch.
|
||||||
Reference: https://github.com/github/eslint-plugin-github/blob/main/docs/rules/async-preventdefault.md
|
Reference: https://github.com/github/eslint-plugin-github/blob/main/docs/rules/async-preventdefault.md
|
||||||
|
|
||||||
|
If an event listener must be `async`, the `e.preventDefault()` should be before any `await`,
|
||||||
|
it's recommended to put it at the beginning of the function.
|
||||||
|
|
||||||
If we want to call an `async` function in a non-async context,
|
If we want to call an `async` function in a non-async context,
|
||||||
it's recommended to use `const _promise = asyncFoo()` to tell readers
|
it's recommended to use `const _promise = asyncFoo()` to tell readers
|
||||||
that this is done by purpose, we want to call the async function and ignore the Promise.
|
that this is done by purpose, we want to call the async function and ignore the Promise.
|
||||||
|
|
Loading…
Reference in a new issue