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/10 11:25:00 UTC
[jira] [Resolved] (SLING-9580) Make the dependency resolution more
resource-type centric
[ https://issues.apache.org/jira/browse/SLING-9580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Radu Cotescu resolved SLING-9580.
---------------------------------
Resolution: Fixed
Fixed in [commit c36961e|https://github.com/apache/sling-org-apache-sling-scripting-sightly-js-provider/commit/c36961e].
> Make the dependency resolution more resource-type centric
> ---------------------------------------------------------
>
> Key: SLING-9580
> URL: https://issues.apache.org/jira/browse/SLING-9580
> Project: Sling
> Issue Type: Improvement
> Components: Scripting
> Reporter: Radu Cotescu
> Assignee: Radu Cotescu
> Priority: Major
> Fix For: HTL JS Use Provider 1.2.2
>
>
> 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
--
This message was sent by Atlassian Jira
(v8.3.4#803005)