Sure, I understand your point. The key word for me here is not generic: it's composition.
I found lots of components which are coupled to the use case they solve, which in some cases could work just fine (e.g. a very specific component you know that it's going to be used just in one place). But, If you have a component that you'll probably use in more that one place (e.g. a dropdown component), making it composable it's the approach that I'd recommend.
Right, I agree. The conclusion I think we both will agree on is that components that logically should be generic should be generic (e.g. a dropdown menu). With that being said, specific components should not be generic, and one should not chase generality as a development goal, but be logical, and efficient.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Sure, I understand your point. The key word for me here is not generic: it's composition.
I found lots of components which are coupled to the use case they solve, which in some cases could work just fine (e.g. a very specific component you know that it's going to be used just in one place). But, If you have a component that you'll probably use in more that one place (e.g. a dropdown component), making it composable it's the approach that I'd recommend.
Thank you very much for the feedback :)
Right, I agree. The conclusion I think we both will agree on is that components that logically should be generic should be generic (e.g. a dropdown menu). With that being said, specific components should not be generic, and one should not chase generality as a development goal, but be logical, and efficient.