I'd like to prevent myself from using `Color.*` or `MaterialTheme.colors.*` in my codebase and inste...

# detekt

[Colton Idle]

I'd like to prevent myself from using Color.* or MaterialTheme.colors.* in my codebase and instead stick to my custom colors I have defined. What's the best way to enforce this with Detekt?

[Brais Gabin]

ForbiddenImport. It will not prevent you for use it with the full qualified. But normally that’s good enought

[Colton Idle]

I tried using that actually, but I couldn't get

forbiddenPatterns to take a list of forbidden import patterns.

[Colton Idle]

Let me try again. Maybe I didn't wrap it in an array correctly or something.

[Brais Gabin]

I would recommend you to use imports instead of forbiddenPatterns

[Brais Gabin]

I like to use it like this:

imports:
  - value: 'Colors.'
     reason: 'Use out custom colors `x.y.z` instead.'
  - value: ...

[Brais Gabin]

This way the person that reads the error knows how to solve the issue

[Colton Idle]

Oh. I like that. TIL

Let me try!

[Colton Idle]

Just a question.

for your example. Is that possible? "Colors."?

Wouldn't the import be something like x.y.Colors?

[Colton Idle]

Or can that section also take a regex essentially?

[Brais Gabin]

I think that the check is “starts with”. But’ I didn’t check.

[Brais Gabin]

So yes, x.y.Colors would do the work

[Brais Gabin]

Any update in the documentation to make the usage more clear is more than welcome.

[Brais Gabin]

We do our best but we need that the new people point us the issues and help us fixing it. There is a long time since I read that documentation blob sweat smile

[Colton Idle]

https://github.com/detekt/detekt/issues/6088