Merge peer-id & peer-info into one, Merge peer-book into js-libp2p

[daviddias]

We've talked this in a PR but creating a issue so that we don't miss it.

• Merge peer-id & peer-info into one
• Merge peer-book into js-libp2p

[daviddias]

While at it, rename the module name to be libp2p-peer

[jacobheun]

I think what I'd really like to see is for peer-info to go away altogether. What it does could and should, imo, be managed by the peer-book (PeerStore, which would be great to rename as part of pulling this into libp2p to avoid confusion with go and the specs). Everything ultimately gets housed in the PeerStore anyway, so fully centralizing it there would be ideal, and it would remove a layer of complexity.

cc: @vasco-santos

[vasco-santos]

I agree with jacob here! Peerbook should own the responsibilities of peer-info.

+1 on renaming this to PeerStore and I want to get this work done as a groundwork to get to libp2p/specs#164

[daviddias]

I think what I'd really like to see is for peer-info to go away altogether. What it does could and should, imo, be managed by the peer-book

Just note that there are multiple modules that require the concept of a Peer but they don't need to know about a PeerStore. That said, I suggest to give it a try and see how viable it is on the refactor to remove the Class Peer (prev peer-info) altogether, I might be missing some nuances that might make it nicer.

(PeerStore, which would be great to rename as part of pulling this into libp2p to avoid confusion with go and the specs).

👍🏽

[daviddias]

Now that PeerStore is becoming part of js-libp2p with the async await refactor.

Can we also get peer-id and peer-info merged into just peer as well?

[vasco-santos]

Yes, I have on my list to tackle that soon :)

[jacobheun]

Released in 0.28