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

fix(material-experimental): throw better error when trying to use fixture after it has been destroyed #17058

Merged
merged 1 commit into from
Sep 18, 2019

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Sep 11, 2019

Currently before most operations in the harnesses we call fixture.detectChange, however doing so on a destroyed fixture throws a vague error. These changes throw a custom error that should be easier to follow.

@crisbeto crisbeto added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent pr: merge safe target: patch This PR is targeted for the next patch release labels Sep 11, 2019
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Sep 11, 2019
@crisbeto crisbeto force-pushed the harness-cd-after-destroy branch 3 times, most recently from c04a1d0 to 929cb6c Compare September 13, 2019 20:56
@crisbeto
Copy link
Member Author

I've switched it to an error based on the discussion @mmalerba. Can you take another look?

@crisbeto crisbeto force-pushed the harness-cd-after-destroy branch from 929cb6c to 55baae1 Compare September 13, 2019 20:57
@crisbeto crisbeto changed the title fix(material-experimental): avoid error when trying to use harness after fixture is destroyed fix(material-experimental): throw better error when trying to use fixture after it has been destroyed Sep 13, 2019
@mmalerba mmalerba added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Sep 13, 2019
@jelbourn
Copy link
Member

@crisbeto could you rebase?

…ture after it has been destroyed

Currently before most operations in the harnesses we call `fixture.detectChange`, however doing so on a destroyed fixture throws a vague error. These changes throw a custom error that should be easier to follow.
@crisbeto crisbeto force-pushed the harness-cd-after-destroy branch from 55baae1 to 17c951d Compare September 18, 2019 15:04
@crisbeto
Copy link
Member Author

Rebased.

@jelbourn jelbourn merged commit 66c8708 into angular:master Sep 18, 2019
jelbourn pushed a commit to jelbourn/components that referenced this pull request Sep 24, 2019
…ture after it has been destroyed (angular#17058)

Currently before most operations in the harnesses we call `fixture.detectChange`, however doing so on a destroyed fixture throws a vague error. These changes throw a custom error that should be easier to follow.

(cherry picked from commit 66c8708)
@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 Oct 19, 2019
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 cla: yes PR author has agreed to Google's Contributor License Agreement P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants