Crossbow78

Ah, I hadn't thought of the ambiguity with `AsString`. But of course, the same can be said about the current parsing behavior which only considers the _first_ attribute to do...

Thanks for your elaborate response, and for bringing structure into my questions. I agree that separating the condition from the action has a beautiful elegance, and I do miss something...

We're deliberately url-encoding the slashes in order to not affect the request path, so I'm trying to understand why the `%2F` is decoded *before* route matching. With a function route...

Our deployment pipeline retrieves the Function App master key to invoke a HTTP trigger as part of an automated smoke-test after deployment of our application. We notice that this step...

Often running into this myself. This seems somewhat related to issue #28, where the generator does not generate valid property names. I'd suggest a simple approach where the member name...

With version 9.0.1, for me the finish effect does not play when the cooldown *ends*, but rather when the cooldown *starts* I'm talking about regular (non-recharge) abilities...

I tried reproducing this with the `PrefetchCount` set to either 0 or 8, but was unable to with 30+ attempts. It's always hard to draw solid conclusions with these "random"...

Out of curiosity, what does this add compared to the existing `Interleave` operation, other than an exception with imbalanced sequences? Wouldn't it be more elegant to make the second `Interleave`...

Other use-cases could be: * Pick a random "StartDate" in the past, and an optional "EndDate" which must lie after the chosen StartDate * Pick a random "IsCancelled" value, and...

We're deliberately url-encoding the slashes in order to not affect the request path, so I'm trying to understand why the `%2F` is decoded *before* route matching. With a function route...