Skip to content

refactor: enable useUnknownInCatchVariables compiler option #24215

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

Merged
merged 1 commit into from
Jan 17, 2022

Conversation

crisbeto
Copy link
Member

Enables the useUnknownInCatchVariables compiler option and fixes a couple of errors.

Enables the `useUnknownInCatchVariables` compiler option and fixes a couple of errors.
@crisbeto crisbeto marked this pull request as ready for review January 16, 2022 16:22
@crisbeto crisbeto added P2 The issue is important to a large percentage of users, with a workaround target: patch This PR is targeted for the next patch release labels Jan 16, 2022
Copy link
Member

@devversion devversion left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Jan 16, 2022
@andrewseguin andrewseguin merged commit 667a555 into angular:master Jan 17, 2022
andrewseguin pushed a commit that referenced this pull request Jan 17, 2022
Enables the `useUnknownInCatchVariables` compiler option and fixes a couple of errors.

(cherry picked from commit 667a555)
@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 Feb 17, 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 P2 The issue is important to a large percentage of users, with a workaround target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants