-
-
Notifications
You must be signed in to change notification settings - Fork 42
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 support for ktlint fix
with -F
#224
base: main
Are you sure you want to change the base?
Add support for ktlint fix
with -F
#224
Conversation
ktlint fix
with -F
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is confusing, they've shipped a format feature in the lint tool. We already have ktfmt in this repo. Is a user meant to choose one or the other?
|
I don't want to close the PR - we DO want to have auto-fixes for linters that understand them. I think we should raise a discussion on the ktlint repo to see if there's any recommended solution (and not make it Bazel specific - we just want to follow what other users do) |
This is a follow-up to
ktlint
support with an action to patch/autocorrect violations where supported in rules using https://pinterest.github.io/ktlint/1.0.1/install/cli/#format-autocorrect and leveraging existing semantics with rules_lintChanges are visible to end-users: yes
Test plan
./lint.sh --fix --dry-run
thathello.kt
would be updated