Asynchronous events - Next steps?

[arthuro555]

With #3535 coming close to being merged, the next steps need to be clarified. This thread is meant both as a To-Do list for everything asynchronous and to discuss obscure points of it.

To-do:

• Add hot reloading of callbacks
• Add Promise.all equivalent
• Add Promise.any equivalent
• Add Promise.race equivalent
• Allow making asynchronous actions in events functions extensions
• Convert existing extensions to asynchronous
  • Network requests
  • Firebase
  • P2P - In Progress: [P2P] Add a way to check if a connection was successful #3778
  • Filesystem - Done: Add awaitable version of async FS actions #5001
  • Clipboard
• Add asynchronous expressions?
• Add actions with toggelable awaiting

[4ian]

Just to state it here:

Toggelable asynchronicity

Agree. We'll have most of them optionnally async and some of them (like a "Wait actions") forced to be async.

[arthuro555]

How should we implement those optionally async functions, since the async implementations is often pretty different from the synchronous one? I think we should have a setAsyncFunction method for optional asynchrony that will add another function name for the async version. An action purely asynchronous could also just use setAsyncFunction without setFunction instead of our current setAsync to make the API more concise.

[arthuro555]

Progressing the goals with #5001