This repository was archived by the owner on Mar 10, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 110
fix: make pubsub.unsubscribe async and alter pubsub.subscribe signature #260
Merged
Merged
Changes from 2 commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
8237791
spec: pubsub.unsubscribe needs to be async
daviddias ab865a5
spec: update the spec, remove the madness of handling two functions a…
daviddias 4c13425
docs: updates pubsub API docs with agreed method signatures
alanshaw c43f8bc
fix: pubsub subscribe call with options
alanshaw 61d7601
docs: add default value for discover
alanshaw f798597
fix: remove duplicate async.each
alanshaw 2019c45
fix: many fixes for pubsub tests with new async unsubscribe
alanshaw 251cffd
fix: remove .only
alanshaw File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
The handler moves into the options object? That's a bit of a weird pattern, much nicer when it was separated.
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.
I'm torn here. The thing is that promisify'ing things forces a weird arg check case.
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.
I agree with @victorbjelkholm on this one, I'd prefer that the implementation choices in js-ipfs didn't affect the public API.
i.e. I don't think promisify should dictate what our public API looks like even if it means handling some difficult argument combinations.
IMHO the most intuitive API would be this:
Most important and non-optional arguments first, followed by optional args.
That said, if you just renamed the
options
arg to something likedetails
then that would be better.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.
I believe your proposal of:
Pretty much solves the main issue. I like it!