ComposableParamOrder behavior for lambdas with default values

[eygraber]

If I have the following:

@Composable
fun Foo(
  onSelect: (Foo) -> Unit,
  displayMapper: (Foo) -> String = { it.name },
  title: String,
)

then ComposableParamOrder will trigger. To fix it I'd have to move displayMapper to the last position, which would allow it to be a trailing lambda, which isn't ideal in Compose.

[mrmans0n]

Yea, got it. What an incredibly unfortunate combo haha

I'll have to check before reporting the lint violation if there's a possible alternative that doesn't trigger the trailing lambda rule 😬 I don't love tying two rules together (because people might be disabling it but I guess being lenient that one time isn't that big of an issue.