Skip to content
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

Unexpected nested config for 'build>weights'. #2128

Closed
1951FDG opened this issue Nov 25, 2019 · 3 comments · Fixed by #2135
Closed

Unexpected nested config for 'build>weights'. #2128

1951FDG opened this issue Nov 25, 2019 · 3 comments · Fixed by #2135

Comments

@1951FDG
Copy link

1951FDG commented Nov 25, 2019

Steps to Reproduce

Unexpected nested config for 'build>weights'.

build:
  maxIssues: 10
  weights:
     complexity: 2

Workaround

If I comment it out, then no issue occurs

build:
  maxIssues: 10
  weights:
    # complexity: 2

Context

I can't specify custom weights anymore as of version 1.2.0, this worked on Version 1.1.1

Your Environment

  • Version of Detekt used: 1.2.0
  • Version of Gradle used (if applicable): 5.4.1
  • Operating System and version: macOS 10.13.6
@arturbosch
Copy link
Member

Thanks for reporting this. This is a serious regression we need a bugfix release for.

@arturbosch arturbosch added this to the 1.2.1 milestone Nov 25, 2019
@1951FDG
Copy link
Author

1951FDG commented Nov 25, 2019

Np, thanks for looking into it.

@arturbosch
Copy link
Member

For now you could use:

config:
  validation: false
  # or
  excludes: build>weights>.*

to skip validation at all or for this properties.

@arturbosch arturbosch self-assigned this Nov 27, 2019
jcornaz added a commit to jcornaz/kwik that referenced this issue Dec 2, 2019
Verision 1.2.0 has a serious issue: detekt/detekt#2128
Version 1.2.1 breaks the build: detekt/detekt#2152
@lock lock bot locked as resolved and limited conversation to collaborators Mar 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants