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

Feature suggestion: disabling on specific files or directories #5

Open
NorielSylvire opened this issue Feb 21, 2024 · 0 comments
Open

Comments

@NorielSylvire
Copy link

Desired feature:

Ability to disable the plugin for specific files or, even better, directories.

Feature description and examples:

When, as an example, editing lua files, you often get warnings such as "unknown global" or "unknown function" (I ran into these while modding Minetest AND while editing neovim config files.
But you can add certain comments/annotations to a specific line or file to disable that specific warning, or configure the formatter to recognize some globals.

The ideal scenario would be a way to set, at the very least, a way for users to disable the plugin con specific directories, or at least file by file. For example via a comment, an annotation, or a hidden .config/.norminette42-config file with all the filepaths to ignore.

Uses:

Useful when developing unit tests, or doing TDD as for example I tend to make multiple tests for each function to test its limits and I quickly run into the "too many functions in file" warning.

Is it possible for this to get implemented? I don't think I am currently skilled enough to implement this, not even fueled by the power of annoyance from the unwanted warnings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant