Open Gallaecio opened 3 years ago
I could add jsonpath support when/if #181 gets merged.
Should adding support for JSONPath be put on hold until #181 gets merged or can I work on it right now?
I think it should wait, because #181 paves the way making internal changes needed for it.
It could be implemented cherry-picking those internal changes. And if someone wants to push JSONPath to be implemented as soon as possible, I am OK with that approach.
I think Jmespath should be supported first, because it has been actively maintained over the years, and has plenty of resources and documentation. Many developers can find a way to get started. Then we can wait for a better and more robust json parser to appear. This doesn't conflict, just like css doesn't conflict with xpath, both are supported by parsel at the same time.
From @Granitosaurus at https://github.com/scrapy/parsel/issues/25#issuecomment-727887878: