api/v1/user/repos responds with an array of JSON objects, each of which represents a repository.
One of the properties of the repository item is called parent. However in the API documentation, the only fields listed as being in the response for a repository are: id, owner, full_name, private, fork, html_url, clone_url, ssh_url, permissions.
The documentation needs to be updated. JSON-parsing libraries sometimes require you to list all potential properties so they can map to an object automatically (apparently Glassfish's Jersey for Java, for example).
(There actually appears to be quite a few things in the response that aren't listed in the documentation.)
api/v1/user/reposresponds with an array of JSON objects, each of which represents a repository.One of the properties of the repository item is called
parent. However in the API documentation, the only fields listed as being in the response for a repository are: id, owner, full_name, private, fork, html_url, clone_url, ssh_url, permissions.The documentation needs to be updated. JSON-parsing libraries sometimes require you to list all potential properties so they can map to an object automatically (apparently Glassfish's Jersey for Java, for example).
(There actually appears to be quite a few things in the response that aren't listed in the documentation.)