Tristan Swadell

@francislavoie The CEL proto supports variadic arguments at an AST level, but the type checker and interpreter don't currently support variadic functions. Using a list literal as an argument is...

@francislavoie I have found a somewhat convoluted way to provide the experience you originally outlined: ``` method("GET") && path("/foo/*") || path("/foo/*", "/bar/*") ``` The trick is to use CEL `parser.Macro`...

How we are thinking about support for the existing matchers might be a bit different. What I'm aiming would add compile time cost, but minimal runtime cost. 1. Use `parser.Macro`...

@francislavoie no worries. I should be able to get all of the standard http matchers configured, though may have to leave the file matchers as an exercise to be completed...

Regarding Triggers, [Tekton](https://github.com/tektoncd/triggers) implemented CEL-based triggers using the [Knative filtering proposal](https://github.com/knative/eventing/blob/master/docs/broker/filtering.md#examples) from @grantr as a reference. FYI @wlynch

The code here is working as designed, so it's not really a bug, but it probably comes as a surprise if you're used to JavaScript. One of the key elements...

Hi Grant, Good comments and questions. > Perhaps an EnvOption could be added I like this suggestion, but equality should probably work one way due to the support and implementation...

Hi @CatalystG, the missing support for the wrapper types at eval time is a bug. I simply didn't implement it yet (I'll file an issue for it for the 0.3.0...

CEL supports a hard-coded notion of an optional value with proto wrapper types such as `google.protobuf.StringValue`. The optional value may either be `null` or ``. JSON is similarly a union...

This has been updated for all extension functions, but has yet to be implemented for all of the standard operators, including type conversion methods which I think are essential for...