{"action":"closed","issue":{"url":"https://api.github.com/repos/jayway/JsonPath/issues/104","labels_url":"https://api.github.com/repos/jayway/JsonPath/issues/104/labels{/name}","comments_url":"https://api.github.com/repos/jayway/JsonPath/issues/104/comments","events_url":"https://api.github.com/repos/jayway/JsonPath/issues/104/events","html_url":"https://github.com/jayway/JsonPath/issues/104","id":92331892,"number":104,"title":"How to obtain a list of all xpaths from a json document","user":{"login":"robinroos","id":13133023,"avatar_url":"https://avatars.githubusercontent.com/u/13133023?v=3","gravatar_id":"","url":"https://api.github.com/users/robinroos","html_url":"https://github.com/robinroos","followers_url":"https://api.github.com/users/robinroos/followers","following_url":"https://api.github.com/users/robinroos/following{/other_user}","gists_url":"https://api.github.com/users/robinroos/gists{/gist_id}","starred_url":"https://api.github.com/users/robinroos/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/robinroos/subscriptions","organizations_url":"https://api.github.com/users/robinroos/orgs","repos_url":"https://api.github.com/users/robinroos/repos","events_url":"https://api.github.com/users/robinroos/events{/privacy}","received_events_url":"https://api.github.com/users/robinroos/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-07-01T09:47:17Z","updated_at":"2015-10-01T22:28:47Z","closed_at":"2015-10-01T22:28:47Z","body":"Sorry to create an Issue, but I could not find a Forum.  \r\n\r\nI wish to parse Json documents and turn them into tables for use in Fitnesse tests.  To do this I considered obtaining the list of all definite (canonical?) json-path expressions, which would form the left-hand column of the table, and then evaluating each path expression in turn to fill in the right-hand column.\r\n\r\nIn Fitnesse I could then constrain that a specific json-path matched the expected node value.  I could also see what \"supurfluous\" node values existed in the document (otherwise I would just invoke individual xpath expressions in turn without ever having to know the full set of path expressions availabls in a given document.\r\n\r\nSo, any hints as to how to establish the full canonical set of json-path expressions realized in a given json document?\r\n\r\nThanks, Robin."}}