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
Part of #21074. For users who are enrolled in the free connectors program, alpha and beta status pills should have an eye-catching "free" label inside (cf. figma, isolated component and in context); they look like this:
Since the variant means "free as in pizza" and billing is a cloud-specific concern, in a perfect world, this would be implemented as a new cloud-specific component wrapping the existing/general purpose "alpha"/"beta" status pills. But to do that, we'd either have to extract (and far worse, maintain) a nearly-identical-but-cloud-specific connections table or just flagrantly violate the "all cloud-specific components should only be referenced within src/packages/cloud/ API boundary; so let's not do that.
The new pill variant should also be added to the EnrollmentModal which currently has text placeholders Pill #1 and Pill #2: #21396
The text was updated successfully, but these errors were encountered:
Part of #21074. For users who are enrolled in the free connectors program, alpha and beta status pills should have an eye-catching "free" label inside (cf. figma, isolated component and in context); they look like this:
Since the variant means "free as in pizza" and billing is a cloud-specific concern, in a perfect world, this would be implemented as a new cloud-specific component wrapping the existing/general purpose "alpha"/"beta" status pills. But to do that, we'd either have to extract (and far worse, maintain) a nearly-identical-but-cloud-specific connections table or just flagrantly violate the "all cloud-specific components should only be referenced within
src/packages/cloud/
API boundary; so let's not do that.The new pill variant should also be added to the
EnrollmentModal
which currently has text placeholdersPill #1
andPill #2
: #21396The text was updated successfully, but these errors were encountered: