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
As many common component libraries are more about having common styles than having common logic, I think for a lot of users that tagging and exporting components is less important after a dev has reviewed a PR than it is for a designer to review the component.
How it works now (with soft tagging and CI setup):
Developer makes changes to a component
Developer creates PR and asks for code reviews
PR is approved and component is tagged and exported
Designer can review this component on Bit.dev
How it could work:
Developer makes changes to a component
Developer does a "soft export" which creates a preview version and sends it to remote
Designer and other stakeholders have opportunity to view the component and provide feedback through their own means (slack, PR etc)
PR is approved and component is tagged and exported
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
-
As many common component libraries are more about having common styles than having common logic, I think for a lot of users that tagging and exporting components is less important after a dev has reviewed a PR than it is for a designer to review the component.
How it works now (with soft tagging and CI setup):
How it could work:
Beta Was this translation helpful? Give feedback.
All reactions