-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Conversation
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.
Please add some tests to this feature to test its behavior and update the respective documentation. Thank you!
RE: documentation. Do we want to update the README to move all the examples to use this? |
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.
Please could you address the linter error?:
/home/travis/build/ipfs/js-ipfs/src/core/index.js
190:24 error Arrow function should not return assignment no-return-assign
Yes, this should be the recommended way of obtaining a ready node. Separately, I think we should stop advertising the callback API (both in the README and the examples) so predominantly. Instead just document that all the API methods support callbacks. I want new users to be using promises so that when #1670 lands it's easier for them to upgrade. re: the examples here I think we should submit a separate PR to switch them all to using async await style, I'd rather not mix |
@pkafei ping |
Just want to reiterate the scope of this ticket. Here I'm implementing ready promise, and I'll update the README (docs) and add a test. @mikeal and I plan on updating all the callbacks in the |
@pkafei do you need some help getting this finished? |
@alanshaw Yes, I need help writing the test. |
Related to #1762