feat: support scope in component name for bit create command #10088
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Allow specifying scope as part of the component name for bit.cloud scopes: - bit create react my-org.my-scope/hooks/use-session - Eliminates need for separate --scope flag in many cases - Only works for bit.cloud scopes (containing a dot) - Falls back to --scope flag or defaultScope if no scope in name - Each component can have its own scope when creating multiple components
GiladShoham
approved these changes
Nov 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Changes
Implements support for specifying the scope directly in the component name when using
bit create, eliminating the need for the separate--scopeflag in many cases.New Syntax
Instead of:
Implementation Details
parseScopeFromComponentIdStr()method to extract scope from component namemy-org.my-scope--scopeflag or workspace defaultScope if no scope is found in the nameTesting