doxygen-spammer

> This is still marked as a draft, but this looks fine for merge, is there any reason I should not merge this for you? Hmm, I replied to this...

I am happy with the current state/result of the patch, so the pull request is no longer a draft. I also wrote a suggested squash commit message in the pull...

I have the same problem. I can see `line_breaks_after_function_body` in [Style-Config.md](https://github.com/Koihik/LuaFormatter/blob/master/docs/Style-Config.md), but that does not preserve spaces between comments and comments or between comments and other code.

Would it help to convert submodules to subtrees before archiving? Quick internet search yielded: https://stackoverflow.com/questions/28215244/convert-git-submodule-to-subtree Then `git archive` can be used instead of `git-archive-all`, which would fix this issue, #184,...

I agree that there should be a better policy about licensing packages. For example, all my mods are REUSE compliant. (https://reuse.software/spec) But I have to remove the licenses from the...

Indeed. As soon as LuaFormatter keeps SPDX statements functional (i. e. this issue is fixed), I will use it in my CI pipelines.

I want to bump this, because I consider this important. My arguments: * Having to supply the default value in code instead of settingtypes.txt violates the DRY rule. (don’t-repeat-yourself) *...

> badly-made mods that already have their default value in their Lua code out > of sync with what they have in settingtypes.txt. > [...] breaking a few badly-made mods...

> I found this git page of up to [10 million](https://github.com/danielmiessler/SecLists/tree/master/Passwords/Common-Credentials) common passwords you can reference, and have as small as 1000. You could reduce this list to 0 passwords...

No code to reproduce needed, the source code confirms the behavior. > Normally options are before positional arguments in usage messages. > However, vararg options should be after, because they...