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

refactor(multiple): enable noImplicitOverride typescript option #22830

Merged
merged 2 commits into from
Jun 18, 2021

Conversation

devversion
Copy link
Member

Enables the TypeScript noImplicitOverride option and adds
the override keyword where needed.

@google-cla google-cla bot added the cla: yes PR author has agreed to Google's Contributor License Agreement label May 27, 2021
@devversion
Copy link
Member Author

Blocked on Google3 updating to TS 4.3

@devversion devversion added the blocked This issue is blocked by some external factor, such as a prerequisite PR label May 31, 2021
Enables the TypeScript `noImplicitOverride` option and adds
the `override` keyword where needed.
Adds a `yarn run` alias for the `tsc` binary. Since we have
multiple versions of TypeScript installed, Yarn can pick
another version (e.g. from `typescript-4.2`) for linking
the `tsc` binary. This is unexpected because `yarn tsc` should
resolve to the TypeScript version that is not installed through
a Yarn alias. Changing the order in the Yarn lock file does not
help, and it seems expected in the context of Yarn which does not
know which package (regardless of alias or not) to prefer.
@devversion devversion force-pushed the typescript-4.3-with-override branch from a412675 to b5e8231 Compare June 11, 2021 13:39
@devversion devversion changed the title [WIP] refactor(multiple): enable noImplicitOverride typescript option refactor(multiple): enable noImplicitOverride typescript option Jun 11, 2021
@devversion devversion added target: minor This PR is targeted for the next minor release and removed blocked This issue is blocked by some external factor, such as a prerequisite PR labels Jun 11, 2021
@devversion devversion marked this pull request as ready for review June 11, 2021 13:45
Copy link
Contributor

@mmalerba mmalerba left a comment

Choose a reason for hiding this comment

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

ooh nice, didn't know this was a thing

@mmalerba mmalerba added the action: merge The PR is ready for merge by the caretaker label Jun 11, 2021
Copy link
Contributor

@andrewseguin andrewseguin left a comment

Choose a reason for hiding this comment

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

Huh thats neat - thanks for making this change

Copy link
Member

@josephperrott josephperrott left a comment

Choose a reason for hiding this comment

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

LGTM

@mmalerba mmalerba merged commit ebd9a97 into angular:master Jun 18, 2021
amysorto pushed a commit to amysorto/components that referenced this pull request Jun 29, 2021
…gular#22830)

* refactor(multiple): enable `noImplicitOverride` typescript option

Enables the TypeScript `noImplicitOverride` option and adds
the `override` keyword where needed.

* build: add yarn script alias for tsc

Adds a `yarn run` alias for the `tsc` binary. Since we have
multiple versions of TypeScript installed, Yarn can pick
another version (e.g. from `typescript-4.2`) for linking
the `tsc` binary. This is unexpected because `yarn tsc` should
resolve to the TypeScript version that is not installed through
a Yarn alias. Changing the order in the Yarn lock file does not
help, and it seems expected in the context of Yarn which does not
know which package (regardless of alias or not) to prefer.
amysorto pushed a commit that referenced this pull request Jun 30, 2021
…2830)

* refactor(multiple): enable `noImplicitOverride` typescript option

Enables the TypeScript `noImplicitOverride` option and adds
the `override` keyword where needed.

* build: add yarn script alias for tsc

Adds a `yarn run` alias for the `tsc` binary. Since we have
multiple versions of TypeScript installed, Yarn can pick
another version (e.g. from `typescript-4.2`) for linking
the `tsc` binary. This is unexpected because `yarn tsc` should
resolve to the TypeScript version that is not installed through
a Yarn alias. Changing the order in the Yarn lock file does not
help, and it seems expected in the context of Yarn which does not
know which package (regardless of alias or not) to prefer.
@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 Jul 19, 2021
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 target: minor This PR is targeted for the next minor release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants