Skip to content

Conversation

MarcoPolo
Copy link
Contributor

Summary

Unglamarous. Just filling in the missing details of encoding/decoding

Before Merge



### Encoding
### Encoding (Bytes -> String)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know this has been in the spec for like, ever, but is this the right way round? IPLD generally refers to "encoding" as turning an object (string, here) into bytes and "decoding" as getting an object from bytes.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wdyt about String Encoding instead?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it has the same problem since "encoding" is still in the title.

This README was written a long time ago and the ecosystem has coalesced around certain language and conventions since then, I think we should bring this in line with everything else.

Co-authored-by: Alex Potsides <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants