Skip to content

fix(compiler-cli): Always retain prior results for all files#61487

Closed
atscott wants to merge 1 commit intoangular:mainfrom
atscott:adoptAllPriorResult
Closed

fix(compiler-cli): Always retain prior results for all files#61487
atscott wants to merge 1 commit intoangular:mainfrom
atscott:adoptAllPriorResult

Conversation

@atscott
Copy link
Copy Markdown
Contributor

@atscott atscott commented May 19, 2025

This change ensures that prior results for all files are retained even when a request is made such that we only need a shim for a single file. Prior to this change, any prior results that were not part of the request were discarded.

@angular-robot angular-robot bot added the area: compiler Issues related to `ngc`, Angular's template compiler label May 19, 2025
@atscott atscott requested a review from JoostK May 19, 2025 22:20
@ngbot ngbot bot added this to the Backlog milestone May 19, 2025
@atscott atscott added the target: patch This PR is targeted for the next patch release label May 19, 2025

if (existingResults.isComplete) {
// All data for this file has already been generated, so no need to adopt anything.
continue;
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Existing logic so no need to change it now, but this seems suspect to me. If the checker already has state for the source file then it seems incorrect to overwrite that with the old state, without any merging operation. I suspect this logic is irrelevant as no state would be available without having adopted prior results already, at least that's how I'd expect this to work (haven't checked the code)

This change ensures that prior results for all files are retained even when
a request is made such that we only need a shim for a single file. Prior
to this change, any prior results that were not part of the request were discarded.
@atscott atscott force-pushed the adoptAllPriorResult branch from bf3a757 to e73b99a Compare May 20, 2025 16:07
@atscott atscott added the action: merge The PR is ready for merge by the caretaker label May 20, 2025
thePunderWoman pushed a commit that referenced this pull request May 21, 2025
This change ensures that prior results for all files are retained even when
a request is made such that we only need a shim for a single file. Prior
to this change, any prior results that were not part of the request were discarded.

PR Close #61487
thePunderWoman pushed a commit that referenced this pull request May 21, 2025
This change ensures that prior results for all files are retained even when
a request is made such that we only need a shim for a single file. Prior
to this change, any prior results that were not part of the request were discarded.

PR Close #61487
@thePunderWoman
Copy link
Copy Markdown
Contributor

This PR was merged into the repository by commit c71adb1.

The changes were merged into the following branches: main, 19.2.x, 20.0.x

@angular-automatic-lock-bot
Copy link
Copy Markdown

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Jun 21, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker area: compiler Issues related to `ngc`, Angular's template compiler target: patch This PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants