When it comes to React components, props are the API that developers consume. A good API should be obvious, something the developer can guess. You ...
For further actions, you may consider blocking this person and/or reporting abuse
Thank you, Sid. It was very helpful 👋.
How I understood was that, one should specify "what" (declarative) a component should do not "how" (imperative) it should do.
So in the
Switchexample,onClickspecifies "how" a user should interact with it, whileonChangeexposes a general behavior of "what" the component can do.Would you correct my understanding as I could be getting the whole abstraction wrong 😅
That's the perfect way of looking at it!
😄👊
Very good your post. How do you see use this pattern to react-native?
I don't use react-native but I'd say the ideas still make sense .The implementation details might change, but the API would look the same