-
-
Notifications
You must be signed in to change notification settings - Fork 761
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
use same behaviour for valueOrNull as for valueOrDefault #2319
use same behaviour for valueOrNull as for valueOrDefault #2319
Conversation
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.
Execution failed for task ':detekt-generator:verifyGeneratorOutput'.
959> The detekt documentation is not up-to-date. Please build detekt locally to update it and commit the changed files.
Thanks for tackling that! It looks good to me. |
30d2807
to
413ea6f
Compare
- implemented valueOrDefault based on valueOrNull per default - kept a different implementation for Test/YamlConfig as the valueOrDefault does more than valueOrNull (it parses values), due to this, valueOrDefault needs to be overriden (and cannot be based on valueOrNull) in: - ConfigAware - CompositeConfig
413ea6f
to
127ff3a
Compare
@schalkms I have updated the documentation. Moreover, I had to change the PR slightly: |
Codecov Report
@@ Coverage Diff @@
## master #2319 +/- ##
============================================
- Coverage 81.87% 81.86% -0.02%
Complexity 2119 2119
============================================
Files 348 348
Lines 6047 6049 +2
Branches 1108 1110 +2
============================================
+ Hits 4951 4952 +1
Misses 512 512
- Partials 584 585 +1
Continue to review full report at Codecov.
|
-fixes #2316