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

test(material/snack-bar): fix error logs in tests #24074

Merged
merged 1 commit into from
Dec 14, 2021

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Dec 9, 2021

The snack bar tests were logging 'dir-with-view-container' is not a known element errors, because the component wasn't added to the declarations after the entryComponents cleanup. This didn't break the CI, because Angular uses console.error for unknown element errors.

The snack bar tests were logging `'dir-with-view-container' is not a known element` errors, because the component wasn't added to the `declarations` after the `entryComponents` cleanup. This didn't break the CI, because Angular uses `console.error` for unknown element errors.
@crisbeto crisbeto added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent merge safe target: patch This PR is targeted for the next patch release labels Dec 9, 2021
@andrewseguin andrewseguin added the action: merge The PR is ready for merge by the caretaker label Dec 9, 2021
@amysorto amysorto merged commit 65a6066 into angular:master Dec 14, 2021
amysorto pushed a commit that referenced this pull request Dec 14, 2021
The snack bar tests were logging `'dir-with-view-container' is not a known element` errors, because the component wasn't added to the `declarations` after the `entryComponents` cleanup. This didn't break the CI, because Angular uses `console.error` for unknown element errors.

(cherry picked from commit 65a6066)
@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 Jan 14, 2022
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 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.

None yet

4 participants