fix(compiler): StaticReflect now resolves re-exported symbols #10453
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.
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x")
What is the current behavior? (You can also link to an open issue here)
As described in #10451 the
StaticReflector
will not correctly locate the metadata for re-exported symbols if the.d.ts
file for the symbol was not needed in thengc
invocation.What is the new behavior?
The
Collector
now records export declaration information that theStaticReflector
uses to track down the correct.metadata.json
file that contains the metadata for a re-exported symbol.Does this PR introduce a breaking change? (check one with "x")
Other information:
Fixes: #10451