We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
currently, when services return json, folk can only specify a top-level dict key from where to get the response
this doesn't work - it might a list, or not top level, or...
proposal: move to a JSONPath in the response_json_field variable
response_json_field
logic:
$
[0][0]
JSONPath likes to return a list. hmm
str
result[0]
List[str]
The text was updated successfully, but these errors were encountered:
leondz
Successfully merging a pull request may close this issue.
currently, when services return json, folk can only specify a top-level dict key from where to get the response
this doesn't work - it might a list, or not top level, or...
proposal: move to a JSONPath in the
response_json_field
variablelogic:
response_json_field
contains no JSONPath special chars, treat it as a top-level dict key (retaining backward compat)response_json_field
starts with a$
, treat is as a raw JSONPathresponse_json_field
contains JSONPath special chars, treat it as a JSONPath, but prepend a$
(this allows python-like structures such as[0][0]
JSONPath likes to return a list. hmm
str
: return thatstr
result[0]
List[str]
. if we're really nice, we could type check that, and log an error if we don't get it backThe text was updated successfully, but these errors were encountered: