fix(runtime): scope id fix for component children for typescript issue #6041
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
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
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.
This fixes an issue we encountered in several of our projects: when using scoped components, scoped classes for child elements in the component is not set correctly, which causes style problems on the child elements.
Apparently this is caused by usage of a spread operator on a Set of scope ids (it is a known issue on the typescript microsoft/TypeScript#8856), this small fix enables to set the scope ids on child element correctly.
What is the current behavior?
GitHub Issue Number: 6042
What is the new behavior?
Documentation
Does this introduce a breaking change?
Testing
Other information