The current implementation of JetLime is a bad API design! 😞
The library is good for simple use cases but fails to cater to more complex ones.
Why?
The library provides a composable JetLimeView and all the other aspects like items, config, etc can only be passed by objects. This restricts control over the item composables. For example, adding a click listener to individual items is currently impossible. The only possible way is to pass a click listener via the Modifier of the content Composable which is a parameter of the JetLimeItem class. But this makes the content clickable, not the entire item.
Solution
A more robust solution is needed and this API should be redesigned to fit every use case! 🙌🏻
The current implementation of JetLime is a bad API design! 😞 The library is good for simple use cases but fails to cater to more complex ones.
Why?
The library provides a composable
JetLimeViewand all the other aspects like items, config, etc can only be passed by objects. This restricts control over the item composables. For example, adding a click listener to individual items is currently impossible. The only possible way is to pass a click listener via theModifierof thecontentComposable which is a parameter of theJetLimeItemclass. But this makes the content clickable, not the entire item.Solution
A more robust solution is needed and this API should be redesigned to fit every use case! 🙌🏻