https://kotlinlang.org
Join Slack
After #kotliners release! Grab RC15 while its hot - <https://bintray.com/arturbosch/code-analysis/de...
# detekt
a
t
Is there a page to show what's left for the 1.0 release? Thanks b
s
We strive to fix bugs and false positives. I think the following page needs an update. CC @Artur Bosch https://github.com/arturbosch/detekt/projects
a
One blocker is the filename length problem on windows when creating a process in the gradle plugin #1686. Additionally I would say #1685.
t
Is fixing all false-positives a hard requirement for 1.0? Other static analysis tools also have false-positives. Actually in android-lint, there are some checks that are false positives in majority of the cases. They keep that for awareness of possible issues.
s
Nope, we strive to have as few as possible. Some won't be fixed till type and symbol solving is non-alpha any more.
t
Striving for less is good. But if you aim for the perfect solution for every check the tool would never hit 1.0
s
But if you aim for the perfect solution for every check the tool would never hit 1.0
True. For the rule part we are fine now except the 
UnnecessaryParentheses
rule, which I want to see removed or deprecated anyway. The merging of reports might be a post v1 feature. The current implementation isn't working properly and gets reverted in #1774.
I also think detekt is ready for v1. However, there are some things that need to get reviewed. Please take a look at issue #1206, where we summarize all v1 related things.
CC @Artur Bosch
a
@taso you are right about the false positive thingy. Nope we will just release 1.0 soon. 3flex wanted to have https://github.com/arturbosch/detekt/pull/1801 in which is now approved. So we are ready for the release.
I will start preparing the release PR tomorrow ^^
t
Amazing 🎉
6 Views
Open in Slack
PreviousNext
Powered by

kotlinlang

A modern programming language that makes developers happier.

Powered by