You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to implement what is feasible with HTTPQueryParamMatch in Wasm... today you can "only" get to request.query... which is... leaving a whole lot on the CEL expression author to do on their own. Can we make this easier on them?
The text was updated successfully, but these errors were encountered:
alexsnaps
changed the title
Help(er functions?) to help working with HTTPQueryParamMatch in CEL
Help(er functions?) to make easier to work with HTTPQueryParamMatch in CEL
Oct 25, 2024
Maybe a good start is to expose a Map<String, String>, possibly thru request.query_params, or a helper function parseQueryParams(request.query) that'd split and url_decode the whole string? Would a Map suffice for implementing Predicates based of HTTPQueryParamMatch?
We want to implement what is feasible with HTTPQueryParamMatch in Wasm... today you can "only" get to
request.query
... which is... leaving a whole lot on the CEL expression author to do on their own. Can we make this easier on them?The text was updated successfully, but these errors were encountered: