What should be done when a component has too many inputs and events? Is there such a thing as too ma...

# compose

[Emmanuel]

What should be done when a component has too many inputs and events? Is there such a thing as too many inputs/events from a single component?

MyComponent(
  input1...,
  inputN,
  event1...,
  eventN
)

[Dominaezzz]

Something something... slot api

[Sean McQuillan [G]]

Typically, divide the component up into smaller parts and pass some of the data/events via slots

[Sean McQuillan [G]]

If you actually use that much stuff, it’s ok to make a class to wrap stuff up too (e.g. TextStyle)

[Emmanuel]

@Sean McQuillan [G] like

onAddTrackToPlaylist: (PlaylistTrackEvent) -> Unit = {},
    onRemoveTrackFromPlaylist: (PlaylistTrackEvent) -> Unit = {},

[Sean McQuillan [G]]

That’s fine

[Sean McQuillan [G]]

until you cross 7 params, that’s just a normal large composable

[Emmanuel]

@Dominaezzz I'm looking into slot api thanks

[Colton Idle]

A good example of slot api is the material scaffold api.

[Colton Idle]

Also this is related and applicable to compose:

https://kotlinlang.slack.com/archives/CJLTWPH7S/p1601088624095100

[Emmanuel]

I've looked into slots and it turns out I use it but didn't know what it was called but not what I'm looking for