Well, how is that useful here? (Just a question, expecting an answer which poses a real need for the feature). Also, i need to figure out where i'll display the path? (please tell me if you have something specific in mind).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
+1 for this feature
I think "Plugin commands" context menu is good place for this.
How is that useful here?
Often working with Json we need get value of concrete node. Working with path will make retriieving access to required node much simpler.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well, how is that useful here? (Just a question, expecting an answer which poses a real need for the feature). Also, i need to figure out where i'll display the path? (please tell me if you have something specific in mind).
+1 for this feature
I think "Plugin commands" context menu is good place for this.
How is that useful here?
Often working with Json we need get value of concrete node. Working with path will make retriieving access to required node much simpler.
Just to make sure, are you taking about this path, the text under the label.
I think it would be better if i display the path to the selected node on a text field in the JSON Dialog.
Interesting things - there is no standart for JsonPath.
But there are a lot of custom implementation:
https://github.com/search?q=jsonpath&ref=cmdform
(Even i create my own little implementation: https://github.com/msangel/JsonPath-Gson/blob/master/GsonPath.java for use in current project)
most of then are implementing draft from
http://goessner.net/articles/JsonPath/
As for place for displaying - for me there is no difference.
UPD:
on http://json.org/ in page bottom there is a link, pointing to same article, so probably we can consider that draft as standart
Last edit: modernskyangel 2013-06-24