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
Consider this object:
{ "foo": { "": { "bar": { "baz": 123 } } }
The following path returns [123], as expected:
[123]
jmespath.search('foo."".bar.*', test) [123]
However, when I put a wildcard in place of the key which is an empty string, I don't get a result:
jmespath.search('foo.*.bar.*', test) is None True
This is strange, because if I don't specify the second wildcard, the first one works and I do get a result:
jmespath.search('foo.*.bar', test) [{'baz': 123}]
I've asked on gitter and have been advised this might be a bug and not my misunderstanding of the JMESPath syntax.
I'm on JMESPath version 0.9.4, installed by pip on Python 3.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Consider this object:
The following path returns
[123]
, as expected:However, when I put a wildcard in place of the key which is an empty string, I don't get a result:
This is strange, because if I don't specify the second wildcard, the first one works and I do get a result:
I've asked on gitter and have been advised this might be a bug and not my misunderstanding of the JMESPath syntax.
I'm on JMESPath version 0.9.4, installed by pip on Python 3.
The text was updated successfully, but these errors were encountered: