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
@antfu suggested to try out to support this, so plugin authors can define their own TypeScript definitions and eslint-define-config would then just use these.
So code in the specific plugin projects would look like this:
importtype{DeprecationRuleConfig}from'./rules/deprecation/deprecation';declare module 'eslint-define-config'{interfaceRules{/** * Do not use deprecated APIs. * * @see [deprecation](https://github.com/gund/eslint-plugin-deprecation) */'deprecation/deprecation'?: DeprecationRuleConfig;}}
importtype{AdjacentOverloadSignaturesRuleConfig}from'./rules/typescript-eslint/adjacent-overload-signatures';// ...declare module 'eslint-define-config'{interfaceRules{/** * Require that function overload signatures be consecutive. * * @see [adjacent-overload-signatures](https://typescript-eslint.io/rules/adjacent-overload-signatures) */'@typescript-eslint/adjacent-overload-signatures'?: AdjacentOverloadSignaturesRuleConfig;// ...}}
The text was updated successfully, but these errors were encountered:
That would be nice, especially now with the Flat Config users can alias plugins to have different prefixes, this would also such configs still provide type safety
Vue has something like this: https://vuejs.org/guide/typescript/options-api.html#augmenting-global-properties
@antfu suggested to try out to support this, so plugin authors can define their own TypeScript definitions and
eslint-define-config
would then just use these.So code in the specific plugin projects would look like this:
The text was updated successfully, but these errors were encountered: