-
Notifications
You must be signed in to change notification settings - Fork 37
Conversation
re 1: I am not sure that is possible with IPLD/cbor as I don't know if they actually allow anything else than a map at the top level |
@dignifiedquire: I think that should be just an IPFS object (not an ipld one). It is just a hash that resolves to a file (although we need to figure out how to store numbers & co) |
You can just run |
After rereading the spec |
@dignifiedquire thanks for this! My tests did not test this yet and I will remove the block then(I will address the need of this feature in a different place). We haven't yet solved 2 (correct?) |
I used your previous suggestion on just using
I got:
|
Just got word from @jbenet and merkle paths are allowed to, need to fix the resolver for that |
Merged and fixed all cases except for the string one, which will not work in this way and I don't think will be needed at this level as all ipfs objects at the end of the day will become IPLD objects anyway. |
I created a new block called
across linked objects
,inside this block there is another block
where links are multihashes
,since in my view links could also be paths e.g.
{name: {@link: /hash/person/name}}
and I expectwhere links are paths
to happen soon (I can just remove it for now)The tests are not passing:
{about: {'@link': 'hash'}}
and I look for/about
, the link should be resolved, instead of returning{'@link': 'hash'}
friends/0/bob
(my reference spec is both the ipld one and my attempt for ip-paths)