yada

martinklepsch 2018-01-24T10:44:43.000141Z

Is there a way to match all “segments” after a certain point as a list param? e.g. /yada/yada/1.2.10/doc/basics/getting-started/ would have a param :doc ["basics" "getting-started"]?

maleghast 2018-01-24T13:58:50.000441Z

Hello All…

maleghast 2018-01-24T13:59:02.000166Z

Does yada cache responses by default..?

maleghast 2018-01-24T13:59:52.000429Z

I have an endpoint that is returning the same result over and over, but when I run the underlying function (that creates the response for the Yada Resource) in my REPL I get what I expect, a different result time after time.

dominicm 2018-01-24T16:14:15.000909Z

@martinklepsch bidi has no notion of segments

dominicm 2018-01-24T16:14:34.000665Z

@maleghast What happens if you curl it?

maleghast 2018-01-24T16:16:19.000712Z

@dominicm - @mccraigmccraig helped me out - I was being a dumbass in the way I was defining my Yada resource.

maleghast 2018-01-24T16:16:25.000071Z

Thanks though!

dominicm 2018-01-24T16:16:51.000079Z

Ah you, set it to the constant. I was suspect of that 🙂

maleghast 2018-01-24T16:25:20.000246Z

Yep - was n00b-ish in the extreme, and if I had really__ been thinking about it I would have spotted it myself.

maleghast 2018-01-24T16:25:31.000308Z

Thanks for getting back to me though 🙂

martinklepsch 2018-01-24T17:00:36.000037Z

@dominicm I figured, so what would be a good way of dealing with this?

malcolmsparks 2018-01-24T17:19:43.000534Z

@martinklepsch each bidi handler can say it matches a path, when asked, whether or not it matches all the remaining path or the start of it

dominicm 2018-01-24T18:19:01.000669Z

To build on ^, you can then split the remainder into segments yourself.

danielcompton 2018-01-24T22:51:13.000356Z

@martinklepsch there is also Yada subresources which you might be looking for?