Async API changes may break plugins
See original GitHub issueMost of the exported functions from the Etherpad internals will no longer take callback parameters in Etherpad 1.8+ (see #3540) and return Promises instead. This may break plugins that rely on those functions.
If backwards compatibility is required one solution may be to use the nodeify
module to conditionally wrap the invocations of those exported functions.
Issue Analytics
- State:
- Created 5 years ago
- Comments:15 (14 by maintainers)
Top Results From Across the Web
Overview | AsyncAPI Initiative for event-driven APIs
Diff is a library that compares two AsyncAPI documents and provides information about the differences by pointing out explicitly information like breaking ......
Read more >Async afterEach hook breaks ready and doneEach hooks #449
Async afterEach hooks such as: $docsify.plugins = [].concat(install, $docsify.plugins) ... But even if we make doneEach async, that might break something.
Read more >CoffeeScript
The structure and properties of CoffeeScript's AST are not final and may undergo breaking changes between CoffeeScript versions; please open an issue if...
Read more >Create and use Custom APIs (Microsoft Dataverse)
A Custom API may include logic implemented with a plug-in. ... Such changes could break code written for the original definition of the ......
Read more >Node.js v19.3.0 Documentation
new AsyncLocalStorage([options]); asyncLocalStorage.disable(); asyncLocalStorage. ... Bugs or behavior changes may surprise users when Experimental API ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
We should probably add some sort of Etherpad API versioning to the internal modules (collectively, not per module) so that the /admin page can indicate which plugins are compatible.
We can close this issue, now that the first point release (1.8.3) after the async rewrite (1.8.0) is ready to be released, and the few actively maintained plugins have been adapted.
Thanks.