fix(compile): avoid ignoring components that their ComponentMap is missing #7183
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
GiladShoham
approved these changes
Mar 22, 2023
GiladShoham
pushed a commit
that referenced
this pull request
Mar 26, 2023
This is a regression caused by #7183. When a component is coming from the scope (happens when loadAspects from scope fails, which is register to `onAspectLoadErrorSlot`), don't try to compile it, otherwise, it throws ComponentNotFound.
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.
from the ConsumerComponent instance.
Although it should not happen. It did happened due to a different bug. Regardless, no need to check for this rootDir anymore, because on Harmony all components have rootDir.