So I think that there is a broader issue here not ...

# detekt

[pavlospt]

So I think that there is a broader issue here not just regarding ObjectPropertyNaming. I have tried changing almost every regex in the config and still get specific issues reported, which is wrong. That leads me to think that custom values are not picked up. I am worried that I might have broken something when added LazyRegex in the sense of a Config picking up custom values and instantiating those Regexes instantly, but later on these fields being mutated and essentially nullified, leading to LazyRegex picking up the default value when it’s time to execute for the first time.

I am not sure if my thoughts are towards the correct direction, but it seems urgent enough to resolve this before going for v1.0.0.

[mauin]

One thing I've checked and which was quite helpful is using the --debug flag as it will print the whole config that is going to be used in a parsed form.

That should allow us to verify if the problem lies somewhere in parsing the config or if the config is correct but something is using it incorrectly.

Thanks for looking into this @pavlospt!

[pavlospt]

It’s the latter as the printed form is correct!

[mauin]

Okay, that's already very good to know

[pavlospt]

@mauin if you investigate it and/or need any help further ping me 🙂

[mauin]

I unfortunately won't have time the rest of this week. I might be able to look into it a bit on the weekend but cannot guarantee that

[mickele]

I’m having the same issue with RC9 and I suspect the same, custom patterns are not being respected it seems.

[skennedy]

yeah, --debug prints out the correct config for me, but it’s not respecting it