Skip to content

fix(core): change defer block fixture default behavior to playthrough#54088

Closed
cexbrayat wants to merge 1 commit intoangular:mainfrom
cexbrayat:fix/default-defer-behavior
Closed

fix(core): change defer block fixture default behavior to playthrough#54088
cexbrayat wants to merge 1 commit intoangular:mainfrom
cexbrayat:fix/default-defer-behavior

Conversation

@cexbrayat
Copy link
Member

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • angular.io application / infrastructure changes
  • Other... Please describe:

What is the current behavior?

This is a followup to #53956

I think the default behavior needs to be changed in TestBedCompiler as well to have an effect.
I tested with v17.2.0-next.0, and the current default behavior is still Manual unless I missed something.

What is the new behavior?

The default behavior is now Playthrough

Does this PR introduce a breaking change?

Other information

@pullapprove pullapprove bot requested a review from AndrewKushnir January 26, 2024 11:23
@cexbrayat cexbrayat force-pushed the fix/default-defer-behavior branch from 63367e7 to 5a2c333 Compare January 26, 2024 11:32
This is a followup to angular#53956

The default behavior needs to be changed in `TestBedCompiler` as well to have an effect.
@cexbrayat cexbrayat force-pushed the fix/default-defer-behavior branch from 5a2c333 to 49127fe Compare January 26, 2024 11:51
@jessicajaniuk
Copy link
Contributor

jessicajaniuk commented Jan 26, 2024

I'm confused. We should have already changed this in #53956.

Update: Ah I see. I missed the test bed compiler change.

Copy link
Contributor

@jessicajaniuk jessicajaniuk left a comment

Choose a reason for hiding this comment

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

LGTM

private testModuleRef: NgModuleRef<any>|null = null;

private deferBlockBehavior = DeferBlockBehavior.Manual;
private deferBlockBehavior = DEFER_BLOCK_DEFAULT_BEHAVIOR;
Copy link
Contributor

Choose a reason for hiding this comment

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

Looks like this is what we missed. Thanks for catching this.

@jessicajaniuk jessicajaniuk removed the request for review from AndrewKushnir January 26, 2024 14:54
@jessicajaniuk jessicajaniuk added action: merge The PR is ready for merge by the caretaker area: core Issues related to the framework runtime target: patch This PR is targeted for the next patch release labels Jan 26, 2024
@ngbot ngbot bot added this to the Backlog milestone Jan 26, 2024
jessicajaniuk pushed a commit that referenced this pull request Jan 26, 2024
…#54088)

This is a followup to #53956

The default behavior needs to be changed in `TestBedCompiler` as well to have an effect.

PR Close #54088
@jessicajaniuk
Copy link
Contributor

This PR was merged into the repository by commit 037b79b.

nikvarma pushed a commit to nikvarma/angular that referenced this pull request Jan 31, 2024
…angular#54088)

This is a followup to angular#53956

The default behavior needs to be changed in `TestBedCompiler` as well to have an effect.

PR Close angular#54088
@angular-automatic-lock-bot
Copy link

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 Feb 26, 2024
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: core Issues related to the framework runtime target: patch This PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants