-
Notifications
You must be signed in to change notification settings - Fork 459
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Support ktlint 0.50.0
and drop support for 0.47.0
#1748
Support ktlint 0.50.0
and drop support for 0.47.0
#1748
Conversation
An additional note: |
Sorry for the slow review, this is great!
That would be fantastic, thanks! I'll merge and release as soon as that is complete. |
…uleSetId}` properties and loading all current `RuleSetProvider`s
Expected impact of the removal of |
…pdate-0.50.0 # Conflicts: # plugin-gradle/CHANGES.md
The NPM
|
Released in |
Closes #1741
Please DO NOT FORCE PUSH. Don't worry about messy history, it's easier to do code review if we can tell what happened after the review, and force pushing breaks that.
Please make sure that your PR allows edits from maintainers. Sometimes its faster for us to just fix something than it is to describe how to fix it.
After creating the PR, please add a commit that adds a bullet-point under the
[Unreleased]
section of CHANGES.md, plugin-gradle/CHANGES.md, and plugin-maven/CHANGES.md which includes:If your change only affects a build plugin, and not the lib, then you only need to update the
plugin-foo/CHANGES.md
for that plugin.If your change affects lib in an end-user-visible way (fixing a bug, updating a version) then you need to update
CHANGES.md
for both the lib and all build plugins. Users of a build plugin shouldn't have to refer to lib to see changes that affect them.This makes it easier for the maintainers to quickly release your changes :)
Additional notes for discussion:
wrapping
that changes the formatting ofresources/kotlin/ktlint/basic.dirty
. I createdbasic-old.clean
for KtLint < 0.50.0 and changedbasic.clean
to wrap the semicolon-separated lines.KtLintCompat0Dot50Dot0Adapter
constructs aKtLintRuleEngine
with the default value oftrue
forenableKotlinCompilerExtensionPoint
. We may want this to be user-configurable to help people debug their custom rule providers. More info here: Remove usages of ExtensionsArea.registerExtensionPoint(java.lang.String, java.lang.String, com.intellij.openapi.extensions.ExtensionPoint.Kind) pinterest/ktlint#1981EditorConfigDefaults.Companion.load
supports adding custom property types to parse from the.editorconfig
, in addition to the defaults. Another potential location for user-configuration.