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
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: