Details
-
Bug
-
Resolution: Fixed
-
Major
-
5.1
-
Integration
-
N/A
-
N/A
-
Description
For example if we have as input:
<a href="something#other">
We wrongly consider it of type "url" whereas it should be considered of type "path".
Here's what I'm implementing:
/** * Recognize the passed reference and figure out what type of link it should be: * <ul> * <li>UC1: the reference points to a valid URL, we return a reference of type "url", * e.g. {@code http://server/path/reference#anchor}</li> * <li>UC2: the reference is not a valid URL, we return a reference of type "path", * e.g. {@code path/reference#anchor}</li> * <li>UC3: there is an anchor but no reference, we return a reference of type "doc", * e.g. {@code #anchor}. In this case we point to the current content. </li> * <li>UC4: the reference is empty, we return a reference of type "doc". In this case we point to the current * content. </li> * </ul> * * @param rawReference the full reference (e.g. "/some/path/something#other") * @return the properly typed {@link ResourceReference} matching the use cases */
Attachments
Issue Links
- relates to
-
XRENDERING-306 Fragment links with no markers are badly converted to XWiki 2.1 syntax
- Closed