A modern programming language that makes developers happier.

kotlinlang

Hi guys!
Do you think it makes sense to skip the `LongMethod`  rule for `@Composable`  functions?
I've had the need to suppress it multiple times the more I write compose.
It can happen because of multiple lambdas, decision making, or any other reason.

Do you think it would be a good addition to change the current function to accept a new config like `ignoredAnnotations`  so that we can configure it? What are your toughts?

Thank you!

That's doable right now. Search for suppressors on detekt to learn how to configure it.

But I'm not sure about if it's a good idea. It's right that there are cases where it's not possible but in general I find that when the function is too long it's because I could create sub components

I’ll take a look at those. Thank you for your feedback!
We model stuff with sealed classes and have composables that just exist to make decisions and propagate stuff

I guess the biggest pain point is the amount of lambdas we need to pass around from the screen component until the multiple composables

We might be doing something wrong honestly :sweat_smile: 

I was not aware of these Suppessors. Worked like a charm. :thank-you-color: