Skip to content
New issue

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

Implement auto-discovery of plugins #155

Open
illright opened this issue Dec 22, 2024 · 0 comments
Open

Implement auto-discovery of plugins #155

illright opened this issue Dec 22, 2024 · 0 comments
Assignees
Labels
PRIORITY | HIGH Important and significant TYPE | enhancement New feature or request
Milestone

Comments

@illright
Copy link
Member

When the config file isn't present, the linter should auto-detect what plugin is installed by searching package.json that contains it for steiger-plugin-*, @*/steiger-plugin, or @*/steiger-plugin-*, as ESLint suggests in its docs for plugin creators:
image

This will allow us to stop defaulting to the FSD ruleset when no config is present, and as such, remove the dependency from steiger on @feature-sliced/steiger-plugin

@illright illright added this to the 0.6.0 milestone Dec 22, 2024
@illright illright added PRIORITY | HIGH Important and significant TYPE | enhancement New feature or request labels Dec 22, 2024
@illright illright self-assigned this Dec 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PRIORITY | HIGH Important and significant TYPE | enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant