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
Remove Layer group block #1019
Remove Layer group block #1019
Conversation
f0e996c
to
20c13eb
Compare
Are you able to provide a live demo? |
check the live demo |
@@ -13,3 +13,6 @@ | |||
/examples/simple.min.js | |||
contribs/gmf/fonts/FontAwesome* | |||
contribs/gmf/fonts/fontawesome* | |||
|
|||
.idea/ | |||
tags |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Better to start with a /
to be sure that's come from the root folder (same for fonts)...
This PR could be affected by the following PR #1011 since the LayerTree behavior has been modified |
@@ -170,20 +157,41 @@ ngeo.LayertreeController = function($scope, $element, $attrs) { | |||
* @type {number} | |||
* @export | |||
*/ | |||
this.uid = goog.getUid(this); | |||
this.depth = isRoot ? 0 : this.parent['depth'] + 1; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
?? why changing the declaration order here ?
I think something like that was enough for this one <a href="" ng-if="::layertreeCtrl.depth == 1"
ng-click="gmfLayertreeCtrl.removeNode(layertreeCtrl.node)">
<span class="fa fa-trash"></span>
</a> |
8770862
to
a74e1f9
Compare
@fgravin could you check please? |
Good thanks. |
Related to #821