[jira] [Created] (SLING-11984) Sling Resource Merger takes current node structure into consideration (not only parent) when determining inclusion/exclusions of nodes with sling:hideChildren

["Henry Kuijpers (Jira)" <ji...@apache.org>]

Henry Kuijpers created SLING-11984:
--------------------------------------

             Summary: Sling Resource Merger takes current node structure into consideration (not only parent) when determining inclusion/exclusions of nodes with sling:hideChildren
                 Key: SLING-11984
                 URL: https://issues.apache.org/jira/browse/SLING-11984
             Project: Sling
          Issue Type: Bug
    Affects Versions: Resource Merger 1.4.0
            Reporter: Henry Kuijpers


It seems that the following node structure:

/apps/test
+ a
+ b
+ c

/apps/test2 (sling:resourceSuperType=/apps/test)
(sling:hideChildren=!a,!b,*)
+ a (with modifications)
+ d (newly defined)

results in:
a,b
instead of
a,b,d

The d node was added additionally (i.e. a tab in a dialog). It does not make sense to me that we would need to add it in the whitelist of children that we do not want to hide. To me, it seems that sling:hideChildren should only act on what is defined in the parent, not on what is defined in the current structure.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)