Thanks to visit codestin.com
Credit goes to github.com

Skip to content

feat(core): move DOCUMENT token into core #60663

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

Closed
wants to merge 2 commits into from

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Apr 1, 2025

Moves the DOCUMENT token from common into core since it's relevant for lots of SSR use cases and users shouldn't have to install common for it. The token is still exported through common for backwards compatibility.

Moves the `DOCUMENT` token from `common` into `core` since it's relevant for lots of SSR use cases and users shouldn't have to install `common` for it. The token is still exported through `common` for backwards compatibility.
@crisbeto crisbeto added action: review The PR is still awaiting reviews from at least one requested reviewer target: major This PR is targeted for the next major release labels Apr 1, 2025
@crisbeto crisbeto requested a review from devversion April 1, 2025 07:39
@pullapprove pullapprove bot requested review from AndrewKushnir and kirjs April 1, 2025 07:39
@angular-robot angular-robot bot added detected: feature PR contains a feature commit area: core Issues related to the framework runtime area: migrations Issues related to `ng update` migrations labels Apr 1, 2025
@ngbot ngbot bot added this to the Backlog milestone Apr 1, 2025
Adds a migration that moves imports of `DOCUMENT` from `common` to `core`.
const {position, end, toInsert} = current.update.data;
const key = current.projectFile.id + '/' + position + '/' + end + '/' + toInsert;

if (!seen.has(key)) {
Copy link
Member

Choose a reason for hiding this comment

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

We should really come up with something for this 😄

@pullapprove pullapprove bot requested a review from thePunderWoman April 1, 2025 07:46
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.

LGTM

Reviewed-for: public-api

Copy link
Contributor

@thePunderWoman thePunderWoman left a comment

Choose a reason for hiding this comment

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

reviewed-for: public-api

@thePunderWoman thePunderWoman added action: merge The PR is ready for merge by the caretaker and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Apr 1, 2025
thePunderWoman pushed a commit that referenced this pull request Apr 1, 2025
Adds a migration that moves imports of `DOCUMENT` from `common` to `core`.

PR Close #60663
@thePunderWoman
Copy link
Contributor

This PR was merged into the repository by commit accc65c.

The changes were merged into the following branches: main

@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 May 2, 2025
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 area: core Issues related to the framework runtime area: migrations Issues related to `ng update` migrations detected: feature PR contains a feature commit target: major This PR is targeted for the next major release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants