-
Notifications
You must be signed in to change notification settings - Fork 52
refactor: async await #148
Conversation
BREAKING CHANGE: Switch to using async/await and async iterators.
dirkmc
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work Vasco
Left a few nits but otherwise LGTM 👍
767110f to
52d056e
Compare
52d056e to
76a872f
Compare
|
@dirkmc can you have a new pass? We decided to make this change in two different PRs. The first one (this) to move everything to async await, followed by a new one to move |
|
I felt the dht code structure was getting in a point that it was really difficult to maintain. Therefore, I decided to restructure the file structure in order to ease maintainability and new contributions |
jacobheun
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a few suggestions and a couple questions about TODOs, but otherwise this looks good.
Co-Authored-By: Jacob Heun <[email protected]>
6de323d to
ba96e12
Compare
jacobheun
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
In the context of ipfs/js-ipfs#1670 all the API is moving into async
BREAKING CHANGE: Switch to using async/await and async iterators.