-
Notifications
You must be signed in to change notification settings - Fork 27k
fix(core): typing of TestBed Common token. #49997
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
Conversation
Both `ComponentFixtureAutoDetect` and `ComponentFixtureNoNgZone` are mistyped. Tokens are only instantiated with booleans.
pkozlowski-opensource
left a comment
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.
This indeed looks like a bug to me!
Let's see if it lands cleanly in G3 and if so I don't see any particular reason for not including this in v16 as a bug fix (safer to do in v16 where breaking changes are "allowed").
pkozlowski-opensource
left a comment
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.
LGTM
Reviewed-for: public-api
Reviewed-for: fw-testing
jessicajaniuk
left a comment
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: fw-core, fw-testing, public-api
|
The TGP is green |
|
This PR was merged into the repository by commit 5607e0f. |
Both `ComponentFixtureAutoDetect` and `ComponentFixtureNoNgZone` are mistyped. Tokens are only instantiated with booleans. PR Close #49997
|
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. |
Both
ComponentFixtureAutoDetectandComponentFixtureNoNgZoneare mistyped. Tokens are only instantiated with booleans.The documentation also only mentions
booleanas value !I mostly see this as a bugfix as the typing is wrong. But is that breaking change acceptable ?
PR Type
What kind of change does this PR introduce?
Does this PR introduce a breaking change?