-
Notifications
You must be signed in to change notification settings - Fork 39
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
Ktlint 0.44.0, Kotlin 1.6.10 #1215
Conversation
That's actually funny, that diktat-snapshot workflow passes. I.e., the project can build and run at least via maven plugin, but the error is simply in our tests infrastructure. |
Ktlint 0.44 also has (finally) a proper logging framework integration. We should check it in our plugins, where for both maven and gradle a slf4j-compatible logger is already available. |
### What's done: * Experiment: change serialization invocation
### What's done: * Experiment: change serialization invocation
…patch-1 # Conflicts: # diktat-rules/src/test/kotlin/org/cqfn/diktat/ruleset/smoke/DiktatSmokeTest.kt
### What's done: * Experiment: new kotlin, old ktlint
Codecov Report
@@ Coverage Diff @@
## master #1215 +/- ##
============================================
- Coverage 83.88% 82.40% -1.49%
+ Complexity 2551 2550 -1
============================================
Files 105 105
Lines 7198 7205 +7
Branches 1951 2018 +67
============================================
- Hits 6038 5937 -101
+ Misses 352 351 -1
- Partials 808 917 +109
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
### What's done: * Kltint 0.44.0, exclude logback
Build passes with kotlin 1.6.10 and ktlint 0.43.2 and explicit |
There was a breaking change in pinterest/ktlint#1230: now rule execution order is determined not by order from RuleSetProvider (which we heavily relied on), but rather rules are sorted alphabetically by IDs with ability to tweak order with modifiers. I managed to make our smoke tests pass by copying part of our rules order using modifiers, but it probably needs more testing. |
### What's done: * Kltint 0.44.0, rules execution order
### What's done: * Kltint 0.44.0, rules execution order
very serious change, as we depend on the rule order… |
May be we should assign proper IDs (aka 1,2,3) for rules to save the order? |
We should prepend all rule IDs with padded indices 001, 002, ..., 137 to preserve the original order |
@Arrgentum could you please help with this change? You can commit directly into this branch. Rules should have IDs like |
… tests, run mvn diktat:fix@diktat
…petertrr-patch-1
ListSerializer
inDiktatSmokeTest
isUnitTestContext = false
in tests, because otherwise it breaks smoke testThis pull request closes #1105