Rename unreleased to drafts to avoid confusion #1609
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rename
@primer/components/unreleased
to@primer/components/drafts
--
Picked a name that doesn't conflict with component maturity status - experimental/alpha/beta/stable
& doesn't conflict with package publishing language - published/released/next/apha/beta
Thanks to @pksjce for the suggestion!
--
This causes confusion in where does
drafts
come from?The long term fix would be to modify the scope conditionally by tagging the code block with "drafts":
```javascript live drafts
.For now, the bandaid is the add a comment to ignore the internal silliness and import from the path