You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Radu Cotescu (Jira)" <ji...@apache.org> on 2020/07/21 16:44:00 UTC

[jira] [Updated] (SLING-9599) Make the dependency resolution more resource-type centric

     [ https://issues.apache.org/jira/browse/SLING-9599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Radu Cotescu updated SLING-9599:
--------------------------------
    Description: Checking for non-existing resources is not completely implemented in SLING-9580 - a correct check would look at the Resource's class and the type. However, the previous solution only checks the former.  (was: The current (1.2.0 and before) implementation of the {{org.apache.sling.scripting.sightly.js.impl.use.DependencyResolver}} can be simplified and reduced to two use-cases:
# caller is a JS script - resolve the dependency relative to the script, but taking resource type hierarchy in consideration
# caller is a component script - resolve the dependency relative to the resource type, but traverse the resource type hierarchy if needed)

> Make the dependency resolution more resource-type centric
> ---------------------------------------------------------
>
>                 Key: SLING-9599
>                 URL: https://issues.apache.org/jira/browse/SLING-9599
>             Project: Sling
>          Issue Type: Improvement
>          Components: Scripting
>            Reporter: Radu Cotescu
>            Assignee: Radu Cotescu
>            Priority: Major
>             Fix For: Scripting HTL JS Use Provider 1.2.2
>
>
> Checking for non-existing resources is not completely implemented in SLING-9580 - a correct check would look at the Resource's class and the type. However, the previous solution only checks the former.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)