Skip to content

refactor(cdk/drag-drop): move sorting and positioning logic into a separate class #25044

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
Jun 9, 2022

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Jun 9, 2022

This is an internal reorganization of the drop list to make it easier to eventually add support for mixed orientation. Includes:

  • Moving out all the sorting and positioning-related code out of DropListRef and into a separate class. The existing logic is very specific to our approach that moves items around using transform. The future mixed orientation will likely move the DOM nodes themselves which would've been difficult to manage if we kept the positioning logic within DropListRef.
  • Moves some of the DOM-related utilities into the dom directory in order to reduce clutter in the root of the package.

…parate class

This is an internal reorganization of the drop list to make it easier to eventually add support for mixed orientation. Includes:
* Moving out all the sorting and positioning-related code out of `DropListRef` and into a separate class. The existing logic is very specific to our approach that moves items around using `transform`. The future mixed orientation will likely move the DOM nodes themselves which would've been difficult to manage if we kept the positioning logic within `DropListRef`.
* Moves some of the DOM-related utilities into the `dom` directory in order to reduce clutter in the root of the package.
@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 Jun 9, 2022
@crisbeto crisbeto requested a review from devversion June 9, 2022 09:23
@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Jun 9, 2022
@crisbeto crisbeto self-assigned this Jun 9, 2022
@crisbeto crisbeto merged commit d40da65 into angular:main Jun 9, 2022
crisbeto added a commit that referenced this pull request Jun 9, 2022
…parate class (#25044)

This is an internal reorganization of the drop list to make it easier to eventually add support for mixed orientation. Includes:
* Moving out all the sorting and positioning-related code out of `DropListRef` and into a separate class. The existing logic is very specific to our approach that moves items around using `transform`. The future mixed orientation will likely move the DOM nodes themselves which would've been difficult to manage if we kept the positioning logic within `DropListRef`.
* Moves some of the DOM-related utilities into the `dom` directory in order to reduce clutter in the root of the package.

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

2 participants