wip: allow to group layers#3151
Merged
Merged
Conversation
0bf2541 to
2b6a0fe
Compare
a00b45f to
2990130
Compare
18d667c to
0abe3ec
Compare
750f242 to
b1cb8d6
Compare
f0ce817 to
385909a
Compare
385909a to
de1beda
Compare
d0c9af0 to
3ce41f4
Compare
f37efa2 to
15e4b7b
Compare
Co-authored-by: David Larlet <david@larlet.fr>
Co-authored-by: David Larlet <david@larlet.fr>
Co-authored-by: David Larlet <david@larlet.fr>
Co-authored-by: David Larlet <david@larlet.fr>
Co-authored-by: David Larlet <david@larlet.fr>
notree: we do not allow at all to have children node
during drag'n'drop (eg. for rules)
nochildren: we do not allow to make this node child of
this given node (eg. for a layer which has features)
Co-authored-by: David Larlet <david@larlet.fr>
Co-authored-by: David Larlet <david@larlet.fr>
Co-authored-by: David Larlet <david@larlet.fr>
…ltered out Otherwise, as soon as a filter excludes a parent, this will totally exclude all the descendants, which is not what we want by default. Co-authored-by: David Larlet <david@larlet.fr>
Co-authored-by: David Larlet <david@larlet.fr>
We wanted to be defensive, but this was a bit too much. Co-authored-by: David Larlet <david@larlet.fr>
Co-authored-by: David Larlet <david@larlet.fr>
Co-authored-by: David Larlet <david@larlet.fr>
Co-authored-by: David Larlet <david@larlet.fr>
Also make that when user drop an element before the DOM feedback the drag'n'drop action is cancelled. Co-authored-by: David Larlet <david@larlet.fr>
Co-authored-by: David Larlet <david@larlet.fr>
Propertie should only contain the keys edited by the user, while umap keys should be outside (permissions, editMode, id, rank…). Co-authored-by: David Larlet <david@larlet.fr>
…widgets Co-authored-by: David Larlet <david@larlet.fr>
Co-authored-by: David Larlet <david@larlet.fr>
…t fields Co-authored-by: David Larlet <david@larlet.fr>
Co-authored-by: David Larlet <david@larlet.fr>
Co-authored-by: David Larlet <david@larlet.fr>
Co-authored-by: David Larlet <david@larlet.fr>
We want the user to decide whether the layer they created is a layer or a group. So we can also adapt the UI and only talk about "group" (not "parent"). Co-authored-by: David Larlet <david@larlet.fr>
Co-authored-by: David Larlet <david@larlet.fr>
So we have a better idea that there may be objects below. Co-authored-by: David Larlet <david@larlet.fr>
Co-authored-by: David Larlet <david@larlet.fr>
It breaks a lot of playwright tests because of the alert on top of the map and other dialog/menus. Co-authored-by: David Larlet <david@larlet.fr>
Co-authored-by: David Larlet <david@larlet.fr>
Co-authored-by: David Larlet <david@larlet.fr>
3d3f730 to
b65b55d
Compare
Co-authored-by: David Larlet <david@larlet.fr>
Seems the "hover" event from playwright is a bit unstable. Co-authored-by: David Larlet <david@larlet.fr>
4978019 to
decb7e9
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
awareness of cascading properties=> laterperformance for 'DataLayer.chidren/hasChildren'clone a parent(functionality hidden for now)decide what to do about feature.properties._umap_options (keep or move to other property, like we did for DataLayer._umap_options)=> laterfield name autocompletion for groups=>works, it just only search in group layers, which is expectedcf #2824 #939