JohnnyMorganz

Spent some time examining this further, but it turns out this is a limitation in the dependency we are using to traverse and ignore files. We actually are already specifying...

Interesting idea, which might be nice to have. I think I'll most likely support project-level editorconfig, rather than a global one, so that it is more noticeable what kind of...

There seems to be a relatively new crate for parsing .editorconfig files which looks promising: https://github.com/TheDaemoness/ec4rs This issue hasn't really been tackled yet since there wasn't great support for editorconfig...

Looks like the thing that made it different is the introduction of a comment. I wonder if we should be expanding the function call instead

This is an interesting one, because it leads us onto something else to consider: should StyLua purposefully align items, such as comments? I know its something done in `gofmt`, but...

I'm still not 100% because it opens a gap in the automated formatting. If I were to add it, it would have to be behind an option

I can't remember exactly why this isn't already a thing. In live share all the files are virtual and (I believe) stored in memory. I think we can get around...

Some useful recommendations as well for reference: https://docs.microsoft.com/en-us/visualstudio/liveshare/reference/extensions#known-issues

The style that StyLua preserves here is whether to leave a table expanded, this is checked by looking for a newline character between the first brace and first element in...

Unfortunately, due to the opinionated nature of the formatter, it is highly unlikely that an option will be added for this. I try to limit the number of options as...