Closed FlorianLeChat closed 2 years ago
Having this issue too, stuff like E2 libs don't work well with my automated workflow as they use their own formatting. Example https://github.com/wiremod/wire/blob/147b817eb5af602bd49f4494505fb80bb40e3030/lua/entities/gmod_wire_expression2/core/chat.lua#L51
There were two problems here:
*.lua
selects. *.lua
will not go in recursion, so b/test_b.lua
is not supposed to be selected. To select those, you need double **
, as in **.lua
*.lua
didn't work, even on top level, because the finding algorithm wasn't finding files relative to the given path (in this case test
). The latter has been fixedI've also added **.lua
to the example, so people start wondering what the difference between *.lua
and **.lua
is.
In the linter parameters, it says "
Files to ignore when linting. You can use glob patterns (e.g. "*.lua" or libraries/*.lua)
", after trying to setup my workspace to ignore some files, it seems this parameter is ignored or is not working as intended. To illustrate this issue, here is the structure of my test workspace tree:I have two Lua files containing:
Here is the GLuaLint configuration at the root of my workspace:
Using VSCode or using the executable through the command prompt (
glualint.exe --config "<path_to_test_folder>\.glualint.json" lint "<path_to_test_folder>"
), GLuaFixer keeps showing me warnings about inconsistencies between the C and Lua comments.This issue is even more annoying because I'm using GLuaFixer with GitHub Actions in a repository containing code which shouldn't be linted or altered for every push or pull request. For information, I did my tests on Windows with the latest version and on GitHub using the instructions from here.
I hope I have been sufficiently explanatory and I am ready to give more information if needed. I still don't understand why such a simple thing doesn't work so if it's a mistake on my side, I'm really sorry! 😭