Quick Question: Would you rather have access to the props of a UI Library or have a dev hard-code options you select from when using components in a Design System?
So recently, I wrote an article about adding a wrapper around components from a UI library so you get access to the props from the UI library but you can customize the component before displaying it on the page. At the time, I thought this was the ultimate in component management. The more I think about it though, the more that might not be the best or simply not other Engineers' preference. So I wanted to post the question to everyone.
Please comment here or in the Twitter thread that this will appear in. Thanks so very much!
Top comments (2)
Generally when extending an already existing library, you want to change the programming interface as little as possible. That way if people have experience with said library, they can take their existing knowledge with them. If you provide a completely new programming interface you're responsible for providing good documentation and you have to convince people that it's worth investing the time to learn how to use your library.
+1