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(material/menu): use separate signature for deprecated constructor parameters #24116

Merged

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Dec 17, 2021

Moves the constructor deprecations out into a separate signature in order to make it easier to remove later on and to make the autocompletion in IDEs more accurate.

This is something we've wanted to do for a while, but ViewEngine didn't support multiple constructor signatures.

Also this is meant as a test to check if anything comes up during the presubmit. If it passes, we can roll this approach out to all constructors.

@crisbeto crisbeto added 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 labels Dec 17, 2021
@crisbeto crisbeto requested a review from a team as a code owner December 17, 2021 07:08
…uctor parameters

Moves the constructor deprecations out into a separate signature in order to make it easier to remove later on and to make the autocompletion in IDEs more accurate.

This is something we've wanted to do for a while, but VIewEngine didn't support multiple constructor signatures.

Also this is meant as a test to check if anything comes up during the presubmit. If it passes, we can roll this approach out to all constructors.
@crisbeto crisbeto force-pushed the deprecated-constructor-signature branch from e80fdcf to e0443de Compare December 17, 2021 07:19
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Dec 29, 2021
@josephperrott josephperrott removed the request for review from a team January 4, 2022 21:46
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

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

LGTM

@jelbourn jelbourn added the action: merge The PR is ready for merge by the caretaker label Jan 7, 2022
@wagnermaciel wagnermaciel merged commit b81259e into angular:master Jan 10, 2022
wagnermaciel pushed a commit that referenced this pull request Jan 10, 2022
…uctor parameters (#24116)

Moves the constructor deprecations out into a separate signature in order to make it easier to remove later on and to make the autocompletion in IDEs more accurate.

This is something we've wanted to do for a while, but VIewEngine didn't support multiple constructor signatures.

Also this is meant as a test to check if anything comes up during the presubmit. If it passes, we can roll this approach out to all constructors.

(cherry picked from commit b81259e)
@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 10, 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 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.

4 participants