So the root cause of this bug is that this content is parsed by the relative entity reference parser and the relative entity reference parser returns null for empty references.
[], [.] and [..] are working because they are special keywords interpreted as ("current document", "current space" and "parent space").
But ... is just a regular reference which means <missing space>.<missing space>.<missing document>, but in the case of a "relative" resolve we don't missing pieces. If it was parsed with the "current" resolver it would produce <current space>.<current space>.<current document>.
Thomas Mortagne on 21/Nov/24 14:34
So the root cause of this bug is that this content is parsed by the relative entity reference parser and the relative entity reference parser returns null for empty references.
[], [.] and [..] are working because they are special keywords interpreted as ("current document", "current space" and "parent space").
But ... is just a regular reference which means {{ <missing space>.<missing space>.<missing document>}}, but in the case of a "relative" resolve we don't missing pieces. If it was parsed with the "current" resolver it would produce {{ <current space>.<current space>.<current document>}}.
Hard to make sense of such reference in the relative resolver, so I guess the best is to change the logic to either consider that we don't have a relative resolver or that it's actually an absolute and set it with the absolute one we resolve right after.
Thomas Mortagne on 21/Nov/24 14:37
So the root cause of this bug is that this content is parsed by the relative entity reference parser and the relative entity reference parser returns null for empty references.
[], [.] and [..] are working because they are special keywords interpreted as ("current document", "current space" and "parent space").
But " ..." is just a regular reference which means {{<missing space>.<missing space>.<missing document>}}, but. Problem is that in the case of a "relative" resolve we don't complete missing pieces. If it was parsed with the "current" resolver it would produce {{<current space>.<current space>.<current document>}}.
Hard to make sense of such reference in the relative resolver, so I guess the best is to change the logic to either consider that we don't have a relative resolver or that it's actually an absolute and set it with the absolute one we resolve right after.
This message was sent by Atlassian Jira (v9.3.0#930000-sha1:287aeb6)
If image attachments aren't displayed, see this article.
