Restore the original luacheck configuration setup #647
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rdw-software
force-pushed
the
revert-luacheckrc-rename
branch
2 times, most recently
from
36f0055 to
a7dcdda
Compare
Not sure what the idea was when I renamed it; I guess the error messages from luacheck analyzing its own config were annoying... But IDE support for nonstandard config files is an issue; you have to manually configure it for every workspace in vscode, for example. Since this also allows running luacheck without args in the project root instead of using a dedicated script, which is easier to understand, I guess it's better to just go back to the original (standard) setup.
rdw-software
force-pushed
the
revert-luacheckrc-rename
branch
from
a7dcdda to
dbd733e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Not sure what the idea was when I renamed it; I guess the error messages from luacheck analyzing its own config were annoying... But IDE support for nonstandard config files is an issue; you have to manually configure it for every workspace in vscode, for example.
Since this also allows running luacheck without args in the project root instead of using a dedicated script, which is easier to understand, I guess it's better to just go back to the original (standard) setup.