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
{{ message }}
This repository has been archived by the owner on Mar 12, 2020. It is now read-only.
There didn't seem to be a symmetric way to retrieve an object as written by textile.files.add(anObject, caption, threadId) for 'json' scheme.
it's great that we can pass the original object without stringify, but it is not clear how we can retrieve this object through existing API, I have tried textile.file.content and textile.ipfs.cat, both gave blob instead of the deserialized object.
once we have the new API that can indeed restore the data back to its original form, i.e. calling JSON.stringify() on the json string extracted from internal response blob, it will be great if textile can take an optional reviver like argument so developers can customize the deserialization accordingly, such as creating a Date object when encountering a ISO date string, among others.
The text was updated successfully, but these errors were encountered:
There didn't seem to be a symmetric way to retrieve an object as written by
textile.files.add(anObject, caption, threadId)
for 'json' scheme.it's great that we can pass the original object without stringify, but it is not clear how we can retrieve this object through existing API, I have tried
textile.file.content
andtextile.ipfs.cat
, both gave blob instead of the deserialized object.once we have the new API that can indeed restore the data back to its original form, i.e. calling
JSON.stringify()
on the json string extracted from internal response blob, it will be great if textile can take an optional reviver like argument so developers can customize the deserialization accordingly, such as creating a Date object when encountering a ISO date string, among others.The text was updated successfully, but these errors were encountered: