You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
currently when we want to acess properties of a PyPLN documents, we need to fetch each on a separate request. This impractical.
There should be an diferent url to fetch the properties data.
For example today when we point the browser to a document properties url, such as this http://fgv.pypln.org/documents/57894/properties/ we get back a json object with an array of property urls for that document:
I agree this is important, specially for our use of PyPLN in mediacloud, but not only for that. I think it will be very useful for everyone.
I would propose /documents/<id>/properties/all or /documents/<id>/properties/all_data/ as the endpoint, just so it would still be under /documents/<id>/properties/.
I just realized this is a pypln.web issue. It will involve changes to the REST API itself. Since those changes must be followed by pypln.api, I'll leave this issue open (but if it is ok with you @fccoelho , I'll edit it to reflect this).
I copied the content of the original issue here to the new one in NAMD/pypln.web#134
currently when we want to acess properties of a PyPLN documents, we need to fetch each on a separate request. This impractical.
There should be an diferent url to fetch the properties data.
For example today when we point the browser to a document properties url, such as this
http://fgv.pypln.org/documents/57894/properties/
we get back a json object with an array of property urls for that document:I propose we add a new API endpoint which could have the form of either:
http://fgv.pypln.org/documents/57894/properties_data/
or
http://fgv.pypln.org/documents/57894/properties/gzip
which would return a gzipped JSON with all the data.
The text was updated successfully, but these errors were encountered: