replace ... by ** to clarifiy any depth capability of the endpoint

[fmigneault]

The original text can be ambiguous depending on how one reads .... For example, it could be misinterpreted as "two levels up" and did not communicate the variability of its position. I propose using ** which is a well established glob pattern communicating any nested path natively while avoiding the . character literally employed by API relative URIs.

Proposed Changes:

1. replace ... by ** to clarify any depth capability of the endpoint
2. minor wording change of the initial description that could cause confusing regarding "where" the child links are found

PR Checklist:

• This PR has no breaking changes.
• I have added my changes to the CHANGELOG or a CHANGELOG entry is not required.

[m-mohr]

I don't necessarily find ** easier to understand than ... - ** is a grep thing, I believe? But the textual clarifications make a lot of sense. Left two comments, I find the "parent" usage confusing.

[m-mohr]

#13 might also be of interest to you, @fmigneault

[fmigneault]

I don't necessarily find ** easier to understand than ... - ** is a grep thing, I believe? But the textual clarifications make a lot of sense. Left two comments, I find the "parent" usage confusing.

It is mostly to make a clearer distinction from ../ that are valid relative references.
When reading fast, it is easy to miss counting a dot, and the difference between 2 or 3 means entirely different things (relative vs anywhere). Using **/ makes that even more explicit for users that it means more than a relative link, that it is not a valid link in itself, but a concept.

[m-mohr]

Fair enough... :-)

[m-mohr]

@fmigneault Can you fix the CI? Then I'm happy to merge.

[fmigneault]

@m-mohr Should be fixed now based on the warning.