IPLD resolver API changes

[kumavis]

We've discussed some potential changes for ipld-resolver. I wanted to make sure we're tracking them all.

• get paths only / lazy value lookups ( some objects like etherum-tx's have implicit data (e.g.: fromAddress) that is computed via expensive crypto - we should only return values that were explicitly asked for)
• get external / local paths only
• toJSON + fromJSON - roundtrip (de-)serialize data via json format
• put + patch api IPLD Resolver patch API #66
• text summary - output text that explains the content of a given ipfs-block
• globbing ( this should be handled outside of the resolvers )

[nicola]

@kumavis are you also implementing globbing? See here: ipld/specs#35 (comment) !

I have a soon-to-be-optimized expensive implementation here: https://github.com/nicola/js-ipld-selector -let me know if you are working on it too, so that we can sync!

[kumavis]

@nicola I'm not implementing any of these, they were more like discussion items that I wanted written down somewhere

[daviddias]

get external / local paths only

@kumavis remind me what you mean by that

toJSON + fromJSON - roundtrip (de-)serialize data via json format

We can do .toJSOn ipld/interface-ipld-format#10

text summary - output text that explains the content of a given ipfs-block

Is this for CLI type applications? Could you give examples for the existing formats? Is this like having a .toTXT? Could this be achieved just by using the .toJSON?