chore: add flag for extended scope token syntax @W-17710895 #5211
Conversation
This file contains 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
wjhsf
changed the title
ekashida
reviewed
Feb 11, 2025
it's unused
tag name (x-test) may not match directory name of root component
jhefferman-sfdc
approved these changes
Feb 13, 2025
just removed it yesterday lol
make it more accurate
|
/nucleus ignore --reason "unrelated __lwc issue in webruntime" |
jhefferman-sfdc
approved these changes
Feb 28, 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.
Details
Users shouldn't, but can provide their own scope tokens. We recently disallowed the use of
.in scope tokens. To avoid breaking users who rely on that character, we re-introduce the character behind a runtime flag.Does this pull request introduce a breaking change?
Does this pull request introduce an observable change?
GUS work item