Skip to content

feature: strict config #51

@bigpopakap

Description

@bigpopakap

Did you check the docs?

  • I have read all the docs

Is your feature request related to a problem? Please describe.

I want to enable all rules as errors, but the recommended config enables them as warnings.

Describe the solution you'd like

I would love to have a strict configuration that turns on all rules as errors.

Describe alternatives you've considered

Manually enabling every rule as an error. But if rules are added, I would have to somehow notice that and add it to my config. If rules are removed, I'll have to fix my config to remove that rule. It would be great to avoid this if the package itself came with the strict config, and could stay in sync with the full list of rules.

Additional context

I guess I'm a glutton for punishment and want to be a real stickler in my side project.

Probably this only makes sense if there's solid confidence that any error truly is an error (no false positives). I don't mind if there are false negatives, of course. This package can't catch every edge case, but it's much better than having no linting at all.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions