Explain what it means for a component in "Draft" state

[primer]

Explain what it means for a component in "Draft" state

[lesliecdubs]

👋🏻 Hello @hamza1311, great question and suggestion!

Quoting from this Architectural Decision Record about draft components:

As we work on maturity of our components, we will sometimes need to build components in a parallel track/bundle without breaking existing components. Eventually, the new components would replace the old ones in the main bundle.

This means that draft components are technically "usable," though it's probably safer to avoid consuming them directly as they are likely to change quickly. Drafts will typically be upgraded into the main bundle quickly once the rewrite/major changes are complete.

I'll check in with the team about potentially adding information about drafts to the component lifecycle and we'll add an update here.

[lesliecdubs]

Just a quick note that this is still on our radar. You can expect an update soon!

[urica12]

Yes

[urica12]

component lifecycle

[lesliecdubs]

Hello! We have approved an architectural decision record that will deprecate the "draft" state in favor of using "experimental" instead, which is defined in the component lifecycle documentation.

I'm going to go ahead and close this as completed, but please comment back if there are any further questions!