-
Notifications
You must be signed in to change notification settings - Fork 26.1k
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
Conversation
fixture
of the RouterTestingHarness
fixture
of the RouterTestingHarness
9e8554a
to
f39bab4
Compare
f39bab4
to
0b6075d
Compare
@JeanMeche can you update the commit description to summarize the usefulness of exposing |
There was a problem hiding this 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
0b6075d
to
2758b36
Compare
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
2758b36
to
75c5ffe
Compare
There was a problem hiding this 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
There was a problem hiding this 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
This PR was merged into the repository by commit 0b14e4e. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
…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
…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
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?
Does this PR introduce a breaking change?