Skip to content

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Jun 6, 2021

When an item enters a new drop container, we dispatch an event and run some logic afterwards. The problem is that if the item is destroyed as a result of the event, the logic after the event will throw because dragging was interrupted.

Also fixes that isDragging returns boolean | undefined rather than the specified boolean.

Fixes #22813.

… the `entered` event

When an item enters a new drop container, we dispatch an event and run some logic afterwards. The problem is that if the item is destroyed as a result of the event, the logic after the event will throw because dragging was interrupted.

Fixes angular#22813.
@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 6, 2021
@crisbeto crisbeto requested a review from jelbourn June 6, 2021 07:37
@google-cla google-cla bot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jun 6, 2021
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 Jun 7, 2021
@wagnermaciel wagnermaciel merged commit 0431d81 into angular:master Jun 10, 2021
wagnermaciel pushed a commit that referenced this pull request Jun 10, 2021
… the `entered` event (#22904)

When an item enters a new drop container, we dispatch an event and run some logic afterwards. The problem is that if the item is destroyed as a result of the event, the logic after the event will throw because dragging was interrupted.

Fixes #22813.

(cherry picked from commit 0431d81)
@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 11, 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 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.

bug(Drag and Drop): Drag/drop between connected DropLists in different *ngFor blocks throws error
3 participants