Hi Marco,
I can confirm that your RESTXQ paths were supposed to work as you
expected them to work: If more than one endpoint is found in the first
round, the one with a larger number of path segments should have been
selected as favorite. In our implementation, the one with less
segments was
Thanks for your suggestion Liam!
We've tried this out on the current deployment which involves version
8.6.3 and it didn't fix our specific use case.
My idea here (I'm not sure to make the correct assumption though) is
that the proposition "if multiple candidate functions ar eleft over"
stated
On Fri, 2019-02-22 at 12:05 +0100, Marco Lettere wrote:
> (: Matches anything followed by /input :)
> declare %rest:path("app/{$path=.+}/input")
>function page:inputs($path) { ... };
>
> (: Matches all other all paths starting with "app/" :)
> declare %rest:path("app/{$path=.+}")
>
Hello all,
according to the docs this should be possible:
(: Matches all paths with "app" as first, a number as second, and
"order" as third segment :)
declare %rest:path("app/{$code=[0-9]+}/order")
function page:order($full-path) { ... };
(: Matches all other all paths starting with
4 matches
Mail list logo
