-
Notifications
You must be signed in to change notification settings - Fork 3.4k
fix(interimElement): don't track elements that fail compilation #11471
Conversation
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 looks reasonable, but we need a unit test to make sure that we don't break this again in the future.
Thank you!
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.
@Splaktar any updates on my above comment?
edit: Not sure why this came through as a review instead of a comment and now it says my above comment was made just now when It was written quite a while ago 🤷♂️
078708c
to
a27e312
Compare
@Splaktar I finally got around to adding a test for this. I verified that the test fails in master and passes in this branch. |
prevent interimElements from being tracked as showingInterimElements when they fail to be compiled Fixes: angular#11460
a27e312
to
dea2ab9
Compare
@Splaktar any update on this? 🐔 |
Sorry for the delay on this, it looks good to go! Thank you |
prevent interimElements from being tracked as showingInterimElements
when they fail to be compiled
Fixes: #11460
PR Checklist
Please check that your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
If an interimElement fails to compile it will still be added as a "showingInterimElement"
Issue Number: #11460
What is the new behavior?
Now interimElements will only be tracked in the showingInterimElements list if they successfully compile.
Does this PR introduce a breaking change?
Other information
Unfortunately the showingInterimElements var is private to the InterimElementFactory and so it is not possible to write unit tests for this without adding additional functionality to the source. If the maintainers decide that is necessary I can definitely do so.