[Feature Request] Add support for JMESPath

Building a Selector based on JMESPath in parsel will help ease parsing Json. This will also help scrapy to add methods like add_json and get_json to the ItemLoader. I got this idea from scrapy/scrapy#1005. From what I understand, the Selector in parsel has been built using lxml, how about using jmespath for building a JsonSelector ?

I am not sure if this is the feature to have in this library as Parsel describes itself as a parser for XML/HTML. But adding this feature will add great value to this project.

PS: If the maintainers would like to have this feature in, Than I’d like to contribute to it myself.

[Granitosaurus]

Not to derail this but I’d argue that implementing JSONpath[1] would actually be more fitting for parsel as it is xpath like. For example Jmespath doesn’t support recursive queries (like //node xpath) while Jsonpath does (as $..node); also the whole protocol structure is much more similar to that of xpath.

Ideally it would be great to have both! More and more web is using json and would be great to have one good parser for both html and json.

1 - https://github.com/h2non/jsonpath-ng jsonpath implementation in Python

[xPi2]

How is going this? I’m trying to implement this myself over parsel selector in my own project but I’m sure you know how to do it better.