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

"Property is misspelled or does not exist" error for new rules in default rulesets #2217

Closed
smyachenkov opened this issue Dec 31, 2019 · 2 comments · Fixed by #2227
Closed
Milestone

Comments

@smyachenkov
Copy link
Contributor

I am getting error "Property is misspelled or does not exist" for build of pull request with the new rule #2215

Expected Behavior

CI build completed successfully.

Observed Behavior

> Task :detekt-gradle-plugin:detekt FAILED
io.gitlab.arturbosch.detekt.cli.InvalidConfig: Run failed with 1 invalid config property.
Property 'style>ExplicitCollectionElementAccessMethod' is misspelled or does not exist.

Steps to Reproduce

Create new rule.
Add it to default ruleset provider, for example StyleGuideProvider
Run CI build with this code.

Context

Noticed on the Travis builds of PR with the new rule #2215
https://ci.appveyor.com/project/arturbosch/detekt/builds/29825544

Your Environment

#2215
https://ci.appveyor.com/project/arturbosch/detekt/builds/29825544

@smyachenkov
Copy link
Contributor Author

Is it related to issue #2168?

@schalkms
Copy link
Member

schalkms commented Jan 2, 2020

Yes, it’s related.

schalkms pushed a commit that referenced this issue Jan 7, 2020
Fixes #2217

When a new rule is added before it's available in the version of detekt that the Gradle plugin uses, the config validation fails because the default detekt config file includes a config for the new rule that the Gradle plugin's detekt version doesn't yet know about.
@arturbosch arturbosch added this to the 1.4.0 milestone Jan 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants