You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 4, 2025. It is now read-only.
The current way of building plugins offers no autocompletion, even though it's based on TypeScript. That's because we're exporting relevant functions at the top level. Instead, a plugin should export default an object implementing interface Plugin – this would offer much better guidance to plugin builders.
The text was updated successfully, but these errors were encountered:
I'm not sure I agree with this. The consensus between JS folks seems to be to move away from default (nameless) exports.
In addition, unless you build plugins with a TS/babel step, you can't use import/export at all. Thus this will not help people using the inline plugin editor.
Can't the same be achieved with some declarations.d.ts file?
The current way of building plugins offers no autocompletion, even though it's based on TypeScript. That's because we're exporting relevant functions at the top level. Instead, a plugin should
export default
an object implementing interfacePlugin
– this would offer much better guidance to plugin builders.The text was updated successfully, but these errors were encountered: