[SLING-9657] Same-name JS Use dependencies are not always correctly resolved

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Scripting HTL JS Use Provider 1.2.4
• Fix Version/s: Scripting HTL Testing Content 1.0.20-1.4.0, Scripting HTL Testing 1.0.22-1.4.0, Scripting HTL JS Use Provider 1.2.6
• Component/s: Scripting
• Assignee: Radu Cotescu
• Reporter: Radu Cotescu
• Created: 12/Aug/20 10:05
• Updated: 24/Aug/20 15:05
• Resolved: 12/Aug/20 16:20

Description

When solving JS dependencies using the resource-type hierarchy, the resolution is not always correct.

Example content structure:

/apps/page/
    page.html
    head.js
/apps/project/page
    [sling:resourceSuperType=page]
    page.html
    partials/
        head.html
        head.js

Example calling model:
/apps/project/page/page.html

<div data-sly-include="partials/head.html}"></div>

/apps/project/page/partials/head.html

<div data-sly-use.head="head.js"></div>

With the above setup, the head.js script being select is the one from /apps/page/head.js, instead of the file inside partials. While this takes the resource type hierarchy into consideration, the correct caller is partials/head.html, hence why the resolution should happen "locally".

Issue Links

• is related to: SLING-9619 The JavaScript Use Provider does not allow loading scripts relative to search paths any more
• is related to: SLING-9580 Make the dependency resolution more resource-type centric