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
DAG-CBOR documents should have an option to visualize them against type(s) from user-provided .ipldsch.
Problem
We've found UX papercut identified with @aschmahmann while trying to provide useful interface for exploring DAG built with IPLD Schema tuples.
DAG-CBOR data is just numbers, and IPLD Explorer does not provide a way of leveraging IPLD Schema .ipldsch definitions.
Solution
Perhaps "Add IPLD Schema" button on DAG-CBOR pages?
Details TBD, but I envision two flows:
Ad-hoc: User clicks the button, then selects the .ipldsch file from their disk, and then user selects the type to use. The schema and type choice per CID is remembered locally (cookie/localstorage)
Permalinks: User clicks the button, enters URL of the .ipldsch file, selects the type to use, and both URL and type are persisted in the URL, so the view that uses schema can be shared by copying current URL.
DAG-CBOR documents should have an option to visualize them against type(s) from user-provided
.ipldsch
.Problem
We've found UX papercut identified with @aschmahmann while trying to provide useful interface for exploring DAG built with IPLD Schema tuples.
DAG-CBOR data is just numbers, and IPLD Explorer does not provide a way of leveraging IPLD Schema
.ipldsch
definitions.Solution
Perhaps "Add IPLD Schema" button on DAG-CBOR pages?
Details TBD, but I envision two flows:
.ipldsch
file from their disk, and then user selects the type to use. The schema and type choice per CID is remembered locally (cookie/localstorage).ipldsch
file, selects the type to use, and both URL and type are persisted in the URL, so the view that uses schema can be shared by copying current URL.References and Test Data
bafyreif22uctcerymml3ahgs2ezkcbkxip4fptrn57gh2eiau7vokwrrzm
corresponding to this transactionbafyreifepnsied7dsdqlrz4ok2pmnsipl5qvhyjlupnpjcwl2utxo4xvyy
corresponding to this transaction/api/v1/sig-to-cid/5Tcw5BT8Spsh3pg6nMaVyrydWSZdiN1YVheVXBHyHrUDTzBJR4pQ3GW9bC5ELJhEThWKgYQtSp71wXzsF4oz9wYX
returnsbafyreif22uctcerymml3ahgs2ezkcbkxip4fptrn57gh2eiau7vokwrrzm
The text was updated successfully, but these errors were encountered: