Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(router): exposes the fixture of the RouterTestingHarness #50280

Closed
wants to merge 1 commit into from

Conversation

JeanMeche
Copy link
Member

@JeanMeche JeanMeche commented May 13, 2023

The component exposed by the fixture is not important thus marked as unknown.

Fixes #48855

PR Type

What kind of change does this PR introduce?

  • Feature

Does this PR introduce a breaking change?

  • No

@JeanMeche JeanMeche marked this pull request as ready for review May 13, 2023 22:10
@pullapprove pullapprove bot requested a review from AndrewKushnir May 13, 2023 22:10
@AndrewKushnir AndrewKushnir added action: review The PR is still awaiting reviews from at least one requested reviewer area: router target: patch This PR is targeted for the next patch release labels May 16, 2023
@ngbot ngbot bot modified the milestone: Backlog May 16, 2023
@pullapprove pullapprove bot removed the request for review from atscott May 16, 2023 21:00
@atscott atscott requested a review from alxhub May 19, 2023 15:23
@atscott atscott added target: minor This PR is targeted for the next minor release and removed target: patch This PR is targeted for the next patch release labels May 19, 2023
@atscott
Copy link
Contributor

atscott commented May 19, 2023

Please update to feat. Deferring to @alxhub for review while I'm OOO. FWIW, my opinion is that the fixture should be exposed for the reasons described in #48855

@JeanMeche JeanMeche changed the title refactor(router): exposes the fixture of the RouterTestingHarness feat(router): exposes the fixture of the RouterTestingHarness May 19, 2023
@angular-robot angular-robot bot added the detected: feature PR contains a feature commit label May 19, 2023
@alxhub
Copy link
Member

alxhub commented Jun 9, 2023

@JeanMeche can you update the commit description to summarize the usefulness of exposing fixture?

Copy link
Member

@alxhub alxhub left a comment

Choose a reason for hiding this comment

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

Reviewed-for: public-api

packages/router/testing/src/router_testing_harness.ts Outdated Show resolved Hide resolved
The component exposed by the fixture is not important thus marked as `unknown`.

Exposing the fixture of the `RouterTestingHarness` allows to use the methods & properties of that fixture and makes it compatible with testing libraries relying on `ComponentFixture`

Fixes angular#48855
Copy link
Member

@alxhub alxhub left a comment

Choose a reason for hiding this comment

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

Reviewed-for: public-api

Copy link
Member

@alxhub alxhub left a comment

Choose a reason for hiding this comment

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

Reviewed-for: global-approvers

@alxhub alxhub added action: merge The PR is ready for merge by the caretaker and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Jun 12, 2023
@pkozlowski-opensource pkozlowski-opensource removed the request for review from AndrewKushnir June 14, 2023 10:35
@pkozlowski-opensource
Copy link
Member

This PR was merged into the repository by commit 0b14e4e.

@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 Jul 15, 2023
@JeanMeche JeanMeche deleted the refactor/router-harness branch August 3, 2023 13:37
thomasturrell pushed a commit to thomasturrell/angular that referenced this pull request Aug 29, 2023
…gular#50280)

The component exposed by the fixture is not important thus marked as `unknown`.

Exposing the fixture of the `RouterTestingHarness` allows to use the methods & properties of that fixture and makes it compatible with testing libraries relying on `ComponentFixture`

Fixes angular#48855

PR Close angular#50280
ChellappanRajan pushed a commit to ChellappanRajan/angular that referenced this pull request Jan 23, 2024
…gular#50280)

The component exposed by the fixture is not important thus marked as `unknown`.

Exposing the fixture of the `RouterTestingHarness` allows to use the methods & properties of that fixture and makes it compatible with testing libraries relying on `ComponentFixture`

Fixes angular#48855

PR Close angular#50280
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: router detected: feature PR contains a feature commit target: minor This PR is targeted for the next minor release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Make the ComponentFixture public in new RouterTestingHarness
5 participants