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(multiple): deprecate exported factories #30608

Merged
merged 1 commit into from
Mar 12, 2025

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Mar 9, 2025

There are a bunch of factory functions that made it into our public API as a result of an old ViewEngine limitation where the factories had to be separate variables and had to be exported. With Ivy this isn't necessary and the factories can be inlined. Also they were never meant to be public APIs.

These changes mark them as deprecated so they can be dropped from the public API in v21.

There are a bunch of factory functions that made it into our public API as a result of an old ViewEngine limitation where the factories had to be separate variables and had to be exported. With Ivy this isn't necessary and the factories can be inlined. Also they were never meant to be public APIs.

These changes mark them as deprecated so they can be dropped from the public API in v21.
@crisbeto crisbeto added the target: patch This PR is targeted for the next patch release label Mar 9, 2025
@crisbeto crisbeto requested a review from a team as a code owner March 9, 2025 09:23
@crisbeto crisbeto requested review from mmalerba and wagnermaciel and removed request for a team March 9, 2025 09:23
/**
* @docs-private
* @deprecated No longer used, will be removed.
* @breaking-change 21.0.0
Copy link
Contributor

@andrewseguin andrewseguin Mar 10, 2025

Choose a reason for hiding this comment

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

Shouldn't this be v22, since it'd be deprecated during two major releases (v20, v21)? Or does v19 count as one (feels a little late for that)

Copy link
Member Author

Choose a reason for hiding this comment

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

The way I interpreted it is that it would have to be deprecated during two major versions: 19 and 20.

@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Mar 12, 2025
@crisbeto crisbeto merged commit 810495c into angular:main Mar 12, 2025
21 of 23 checks passed
@crisbeto
Copy link
Member Author

The changes were merged into the following branches: main, 19.2.x

crisbeto added a commit that referenced this pull request Mar 12, 2025
There are a bunch of factory functions that made it into our public API as a result of an old ViewEngine limitation where the factories had to be separate variables and had to be exported. With Ivy this isn't necessary and the factories can be inlined. Also they were never meant to be public APIs.

These changes mark them as deprecated so they can be dropped from the public API in v21.

(cherry picked from commit 810495c)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
action: merge The PR is ready for merge by the caretaker target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants