You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[ ] bug report => Search github for a similar issue or PR before submitting
[X] feature request
[ ] support request => Sorry, we will not be able to answer every support request. Please consider other venues for support requests
Current behavior
Using the component instead of the directive there is a attribute [moves] available. This accepts a boolean. I would like to be able to set this move boolean on a child, not on the container. Now I'm only able to set true; All these items can be moved or no; All these items can not be moved.
Expected behavior
I would like to be able to set this move boolean on a child, not on the container. Now I'm only able to set true; All these items can be moved or no; All these items can not be moved.
Reproduction of the problem
What is the motivation / use case for changing the behavior?
I think that's clear enough in the Expected behavior.
Angular version: 2.x.x
5.0.0
Browser:
Chrome
Language:
Typescript 2.4.2
The text was updated successfully, but these errors were encountered:
I'm submitting a ... (check one with "x")
Current behavior
Using the component instead of the directive there is a attribute [moves] available. This accepts a boolean. I would like to be able to set this move boolean on a child, not on the container. Now I'm only able to set true; All these items can be moved or no; All these items can not be moved.
Expected behavior
I would like to be able to set this move boolean on a child, not on the container. Now I'm only able to set true; All these items can be moved or no; All these items can not be moved.
Reproduction of the problem
What is the motivation / use case for changing the behavior?
I think that's clear enough in the Expected behavior.
Angular version: 2.x.x
5.0.0
Browser:
Chrome
Language:
Typescript 2.4.2
The text was updated successfully, but these errors were encountered: