Open purkhusid opened 2 weeks ago
@purkhusid thanks for reporting this!
I'm afraid the solution -- as I understand it -- is not so trivial at the moment but I have half-started the work to move to Dynamic Attributes instead of the type coercion/inference we're currently doing.
Versions 0.27.1
Steps to reproduce
If you have the following query specification:
The filter value for
response_code
is inferred to be an integer when the spec is passed to e.g. a honeycomb query resource. The filter should infer the value to be a string.The query json ends up as:
but should end up as: