We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It's more difficult to enable the current separate plugin and rule configuration:
{ "plugins": ["@inngest"], "extends": ["plugin:@inngest/recommended"] }
when using the new flat configuration file format.
It's possible to do so with:
import inngestEslintPlugin from "@inngest/eslint-plugin"; export default [ ... inngestEslintPlugin.configs.recommended, ... // other configurations { languageOptions: { ... }, plugins: { "@inngest": inngestEslintPlugin, }, rules: { ... }, }, ]
But it would be much nicer for the configuration to enable the plugin at the same time so this becomes a one-liner.
In addition, it would be very nice to bundle typescript types at the same time, so the import will be typed correctly.
The text was updated successfully, but these errors were encountered:
INN-3610 Update @inngest/eslint-plugin recommended config to enable rules and plugin at the same time
Sorry, something went wrong.
No branches or pull requests
It's more difficult to enable the current separate plugin and rule configuration:
when using the new flat configuration file format.
It's possible to do so with:
But it would be much nicer for the configuration to enable the plugin at the same time so this becomes a one-liner.
In addition, it would be very nice to bundle typescript types at the same time, so the import will be typed correctly.
The text was updated successfully, but these errors were encountered: