You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2025/06/02 16:42:00 UTC

[jira] [Assigned] (SLING-12815) Expose methods to escape/unescape characters which are invalid in Sling Resource names

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

Konrad Windszus reassigned SLING-12815:
---------------------------------------

    Assignee: Konrad Windszus

> Expose methods to escape/unescape characters which are invalid in Sling Resource names
> --------------------------------------------------------------------------------------
>
>                 Key: SLING-12815
>                 URL: https://issues.apache.org/jira/browse/SLING-12815
>             Project: Sling
>          Issue Type: Improvement
>          Components: API
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>            Priority: Major
>             Fix For: API 3.0.0
>
>
> Sling API imposes the following restrictions for resource names:
> # No slash must be used (as used as path separator characters)
> # No names only consisting of dots must be used (as used as relative path specifiers in {{ResourceResolver.getResource()}}.
> Although most resource providers impose additional restrictions there should be some default escape/unescape mechanism which can be used to escape those characters.
> Compare with the discussion at https://lists.apache.org/thread/cbpksrfm30jy070qxxq02qwxrb8l0v2s



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