Ned Twigg
Ned Twigg
The reflection is ugly, but necessary, for reasons described in #187. It's fine to add it as a compile dep to work out what the code needs to be, but...
I *think* it would be the project directory, but I'm not positive. Regardless, Spotless would have to know about the `.editorconfig` file explicitly so that up-to-date checking can work. Perhaps...
Is the `.editorConfig` parsing hierarchical? Or is there only one `.editorConfig` at the project root, and that's it? Spotless is fast because of up-to-date checking, but it's still pretty fast...
One option is `ktlint().editorConfig()`, and `.editorConfig()` means "we search the project directory and all of its parents for .editorconfig (maybe also userhome? that seems very bad for CI)". It doesn't...
Tracking issue for anybody who wants to remove reflection: https://github.com/diffplug/spotless/issues/524
Drive-by documentation improvements are always welcome :)
> I expected this not to depend at all on Spotless, and to simply work The reason Spotless is meddling is to support up-to-date and incremental formatting. In order to...
Now that #1012 has merged, it should be easier to build this if anybody wants to contribute a PR.
Happy to take a PR for it :). I've switched to `ktfmt` and it's been great - stable APIs, less mucking with configuration.
The IDE hook can also read/write from stdin and/or stdout, which is useful for IDE integration. It is difficult to reconcile those features with multiple files, so I will not...