[
https://issues.apache.org/jira/browse/OAK-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13491478#comment-13491478
]
angela commented on OAK-426:
----------------------------
> Both "." and ".." are valid names for items in Tree.
hmm... i would consider this a bug. at least this sounds like
asking for troubles and inconsistencies. what is the use-case behind
allowing for current/parent element in the tree-name?
> However, any additional semantics of paths strings would better be handled
> above this layer
that's what i thought as well when i worked around it the first time.
but i don't want to copy the same test for "." and ".." to different
places. the layer-above doesn't work for me since i am working on the
oak-level. but obviously i was equally fine with a 'normalize' utility
somewhere in the path/name package.
> TreeLocation: Add support for relative paths containing current or parent
> element
> ---------------------------------------------------------------------------------
>
> Key: OAK-426
> URL: https://issues.apache.org/jira/browse/OAK-426
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: core
> Reporter: angela
>
> i just run into another place where i would need to work around
> missing support for the current (".") and parent ("..") element
> in the TreeLocation.
> IMO it would make sense to add this to TreeLocation#getChild... maybe
> even rename it to TreeLocation#getLocation(String relativePath)?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
