[
https://issues.apache.org/jira/browse/OAK-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13494053#comment-13494053
]
angela commented on OAK-426:
----------------------------
that the Tree doesn't handle it is pretty obvious but if it really should not
care is IMHO debatable.
the longer i actually think about the more i have the impression that it was
better to deal with
'.' and '..' wherever the OAK API takes a relative path.
keeping this in a utility might work but i have the feeling that it's really
sensible to do so
and will be prone for errors as there will be many places where that needs to
be enforced.
in addition i simply can't come up with a use-case of having '.' and '..' being
valid names for a
Tree or a PropertyState and since the OAK API is on a different level of
abstraction than the MK I
don't see why we should be bound to the same level of ignorance.
> 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
