You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a question about GitHub's approach to component JavaScript implementation. I understand that you use web components/catalyst wrapped with a ViewComponent when JavaScript interactivity is required (such as for autocomplete functionality). I'm wondering: do you still believe that the component library should export ViewComponents as the primary interface, or have your thoughts evolved regarding web components playing a larger role and being used directly by consuming applications?
For context, we have several applications that don't use Ruby on Rails, which has us reconsidering how to provide our design system components to these applications. We're exploring two main options:
Reimplement the component specifications in a different technology, like React
Build universal web components (like <auto-complete />) that could be used across all our applications directly
My main concern with fully embracing web components is that we might lose the benefits that Ruby/React-first development provides.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have a question about GitHub's approach to component JavaScript implementation. I understand that you use web components/catalyst wrapped with a ViewComponent when JavaScript interactivity is required (such as for autocomplete functionality). I'm wondering: do you still believe that the component library should export ViewComponents as the primary interface, or have your thoughts evolved regarding web components playing a larger role and being used directly by consuming applications?
For context, we have several applications that don't use Ruby on Rails, which has us reconsidering how to provide our design system components to these applications. We're exploring two main options:
<auto-complete />
) that could be used across all our applications directlyMy main concern with fully embracing web components is that we might lose the benefits that Ruby/React-first development provides.
Beta Was this translation helpful? Give feedback.
All reactions