Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add ktlint-configuration-report task to report ktlint configurations #661

Open
JLLeitschuh opened this issue Apr 3, 2023 · 0 comments
Open

Comments

@JLLeitschuh
Copy link
Owner

We get quite a few issues that are maybe rooted in ktlint, and maybe roote in ktlint-gradle. Adding a reporting task that communicates information like "this is what we sent to ktlint" and "this is what ktlint interpreted that to mean", would help with debugging these issues and hopefully give end-users the tools to figure out problems themselves instead of asking us.

Related:

Information ideally provided:

  • Listing the .editorconfig file was actually resolved and is being used
  • What setting has ktlint actually read from that .editorconfig file
  • A summary of the paths the .editorconfig file was applied to
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant