[jira] [Created] (SLING-8933) The IncludeRuntimeExtension doesn't correctly normalise paths when using the path manipulation options

["Radu Cotescu (Jira)" <ji...@apache.org>]

Radu Cotescu created SLING-8933:
-----------------------------------

             Summary: The IncludeRuntimeExtension doesn't correctly normalise paths when using the path manipulation options
                 Key: SLING-8933
                 URL: https://issues.apache.org/jira/browse/SLING-8933
             Project: Sling
          Issue Type: Bug
          Components: Scripting
    Affects Versions: Scripting HTL Engine 1.2.0-1.4.0
            Reporter: Radu Cotescu
            Assignee: Radu Cotescu
             Fix For: Scripting HTL Engine 1.3.2-1.4.0


The {{prependPath}} and {{appendPath}} options passed to {{data-sly-resource}} or {{data-sly-include}} seem to have wrongly been handled by the {{UriManipulationFilter}} until SLING-8896, when the filter was changed to be applied in all other contexts, except for {{data-sly-resource}}, {{data-sly-include}}, {{data-sly-use}}, {{data-sly-call}}, {{data-sly-template}}.

This led to the discovery that the {{data-sly-include}} plugin doesn't correctly normalise the paths when path options are passed. E.g.:

{code:html}
<sly data-sly-include="${'nav.html' @ prependPath='/apps/myproject/components/templates'}"></sly>
{code}

will now fail, since the generated script path will be {{/apps/myproject/components/templatesnav.html}} - notice the missing {{/}} character.



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