Skip to content

Conversation

@crisbeto
Copy link
Member

Currently if somebody attaches a cdkDrag to a non-element node (e.g. an ng-container), a cryptic error will be thrown. These changes log a proper error so it's easier to debug.

@crisbeto crisbeto added the target: patch This PR is targeted for the next patch release label Nov 20, 2018
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Nov 20, 2018
@ngbot
Copy link

ngbot bot commented Nov 27, 2018

Hi @crisbeto! This PR has merge conflicts due to recent upstream merges.
Please help to unblock it by resolving these conflicts. Thanks!

1 similar comment
@ngbot
Copy link

ngbot bot commented Nov 27, 2018

Hi @crisbeto! This PR has merge conflicts due to recent upstream merges.
Please help to unblock it by resolving these conflicts. Thanks!

Copy link
Member

@josephperrott josephperrott left a comment

Choose a reason for hiding this comment

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

LGTM

@josephperrott josephperrott added pr: lgtm action: merge The PR is ready for merge by the caretaker and removed action: merge The PR is ready for merge by the caretaker labels Nov 27, 2018
@ngbot
Copy link

ngbot bot commented Nov 27, 2018

I see that you just added the pr: merge ready label, but the following checks are still failing:
    failure conflicts with base branch "master"

If you want your PR to be merged, it has to pass all the CI checks.

If you can't get the PR to a green state due to flakes or broken master, please try rebasing to master and/or restarting the CI job. If that fails and you believe that the issue is not due to your change, please contact the caretaker and ask for help.

@josephperrott
Copy link
Member

@crisbeto add pr: merge ready after the conflicts are resolved

@crisbeto crisbeto force-pushed the drag-drop-ng-container-error branch from ebc6a2e to 0418466 Compare November 27, 2018 17:50
@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Nov 27, 2018
@crisbeto crisbeto force-pushed the drag-drop-ng-container-error branch from 0418466 to 57b09bb Compare December 2, 2018 15:47
@mmalerba
Copy link
Contributor

mmalerba commented Dec 4, 2018

@crisbeto needs rebase

Currently if somebody attaches a `cdkDrag` to a non-element node (e.g. an `ng-container`), a cryptic error will be thrown. These changes log a proper error so it's easier to debug.
@crisbeto crisbeto force-pushed the drag-drop-ng-container-error branch from 57b09bb to 2943932 Compare December 4, 2018 20:31
@crisbeto
Copy link
Member Author

crisbeto commented Dec 4, 2018

Rebased.

@mmalerba mmalerba merged commit 31f0e6d into angular:master Dec 4, 2018
mmalerba added a commit that referenced this pull request Dec 5, 2018
mmalerba added a commit that referenced this pull request Dec 5, 2018
…correctly if the floating label is disabled" (#14396)

* Revert "fix(drag-drop): error on touch end (#14392)"

This reverts commit 53cecbb.

* Revert "fix(menu): reduce specificity of icon selector (#14389)"

This reverts commit 74e945a.

* Revert "fix(drag-drop): throw better error when attaching to non-element node (#14221)"

This reverts commit 31f0e6d.

* Revert "fix(autocomplete): auto-highlighted first option not display correctly if the floating label is disabled (#13774)"

This reverts commit c99c512.
mmalerba added a commit that referenced this pull request Dec 5, 2018
mmalerba added a commit that referenced this pull request Dec 5, 2018
… in trigger" (#14398)

* Revert "Revert "fix(autocomplete): auto-highlighted first option not display correctly if the floating label is disabled" (#14396)"

This reverts commit aa17fbd.

* Revert "fix(drag-drop): error on touch end (#14392)"

This reverts commit 53cecbb.

* Revert "fix(menu): reduce specificity of icon selector (#14389)"

This reverts commit 74e945a.

* Revert "fix(drag-drop): throw better error when attaching to non-element node (#14221)"

This reverts commit 31f0e6d.

* Revert "fix(autocomplete): auto-highlighted first option not display correctly if the floating label is disabled (#13774)"

This reverts commit c99c512.

* Revert "fix(autocomplete): update template when changing autocomplete in trigger (#13814)"

This reverts commit 904a5ea.
mmalerba added a commit that referenced this pull request Dec 10, 2018
…correctly if the floating label is disabled" (#14396)

* Revert "fix(drag-drop): error on touch end (#14392)"

This reverts commit 53cecbb.

* Revert "fix(menu): reduce specificity of icon selector (#14389)"

This reverts commit 74e945a.

* Revert "fix(drag-drop): throw better error when attaching to non-element node (#14221)"

This reverts commit 31f0e6d.

* Revert "fix(autocomplete): auto-highlighted first option not display correctly if the floating label is disabled (#13774)"

This reverts commit c99c512.
mmalerba added a commit that referenced this pull request Dec 10, 2018
… in trigger" (#14398)

* Revert "Revert "fix(autocomplete): auto-highlighted first option not display correctly if the floating label is disabled" (#14396)"

This reverts commit aa17fbd.

* Revert "fix(drag-drop): error on touch end (#14392)"

This reverts commit 53cecbb.

* Revert "fix(menu): reduce specificity of icon selector (#14389)"

This reverts commit 74e945a.

* Revert "fix(drag-drop): throw better error when attaching to non-element node (#14221)"

This reverts commit 31f0e6d.

* Revert "fix(autocomplete): auto-highlighted first option not display correctly if the floating label is disabled (#13774)"

This reverts commit c99c512.

* Revert "fix(autocomplete): update template when changing autocomplete in trigger (#13814)"

This reverts commit 904a5ea.
josephperrott pushed a commit to josephperrott/components that referenced this pull request Jan 14, 2019
…angular#14221)

Currently if somebody attaches a `cdkDrag` to a non-element node (e.g. an `ng-container`), a cryptic error will be thrown. These changes log a proper error so it's easier to debug.
josephperrott pushed a commit to josephperrott/components that referenced this pull request Jan 14, 2019
…correctly if the floating label is disabled" (angular#14396)

* Revert "fix(drag-drop): error on touch end (angular#14392)"

This reverts commit 53cecbb.

* Revert "fix(menu): reduce specificity of icon selector (angular#14389)"

This reverts commit 74e945a.

* Revert "fix(drag-drop): throw better error when attaching to non-element node (angular#14221)"

This reverts commit 31f0e6d.

* Revert "fix(autocomplete): auto-highlighted first option not display correctly if the floating label is disabled (angular#13774)"

This reverts commit c99c512.
josephperrott pushed a commit to josephperrott/components that referenced this pull request Jan 14, 2019
… in trigger" (angular#14398)

* Revert "Revert "fix(autocomplete): auto-highlighted first option not display correctly if the floating label is disabled" (angular#14396)"

This reverts commit aa17fbd.

* Revert "fix(drag-drop): error on touch end (angular#14392)"

This reverts commit 53cecbb.

* Revert "fix(menu): reduce specificity of icon selector (angular#14389)"

This reverts commit 74e945a.

* Revert "fix(drag-drop): throw better error when attaching to non-element node (angular#14221)"

This reverts commit 31f0e6d.

* Revert "fix(autocomplete): auto-highlighted first option not display correctly if the floating label is disabled (angular#13774)"

This reverts commit c99c512.

* Revert "fix(autocomplete): update template when changing autocomplete in trigger (angular#13814)"

This reverts commit 904a5ea.
@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 Sep 10, 2019
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 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