jmespath / jmespath/jmespath.js
unexpected parse result
- Dominant language
- JavaScript
- Stars
- 847
- Forks
- 101
- PR merge metrics
- No merged PRs in 30d
Description
* `jmespath: ^0.16.0`
```
# good result
jmespath.search({desc: "a55555e"}, "starts_with(desc, 'a')") => true
jmespath.search({desc: "ae55555e"}, "starts_with(desc, 'a')") => true
jmespath.search({desc: "e55555e"}, "desc") => "e55555e"
jmespath.search({desc: "c5555e"}, "starts_with(desc, 'c')") => true
jmespath.search({desc: "f5555e"}, "starts_with(desc, 'f')") => true
# bad result
jmespath.search({desc: "e55555e"}, "starts_with(desc, 'e')") => false # we should get true
jmespath.search({desc: "55555e"}, "starts_with(desc, '5')") => false # we should get true
jmespath.search({name: "e5555e"}, "starts_with(name, 'e')") => false # we should get true
jmespath.search({name: "5555e"}, "starts_with(name, '5')") => false # we should get true
```
it seems that we get error to use `starts_with` for strings that starts with `number` or `e`
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.