Skip to content
This repository has been archived by the owner on Oct 17, 2024. It is now read-only.

Add StreamGroup.mergeBroadcast #90

Merged
merged 1 commit into from
Oct 3, 2019
Merged

Add StreamGroup.mergeBroadcast #90

merged 1 commit into from
Oct 3, 2019

Conversation

natebosch
Copy link
Contributor

No description provided.


expect(merged.isBroadcast, isTrue);

expect(merged.toList(), completion(unorderedEquals(["first", "second"])));
Copy link
Contributor

Choose a reason for hiding this comment

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

does this need to be an unorderedEquals check? In theory these would always come in the order they are emitted by the given streams right?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

🤷‍♂ - it duplicates the existing test... I'll followup on this.

@natebosch natebosch merged commit 7d35ce9 into master Oct 3, 2019
@natebosch natebosch deleted the merge-broadcast branch October 3, 2019 21:33
natebosch added a commit that referenced this pull request Oct 3, 2019
See #90 (comment)

Merged streams forward events synchronously so we do know that
guarantees that events keep their order when forwarded. Since it's not
necessary to allow for ordering changes drop the `unorderedEquals`.

Also refactor to async/await from a `completion` matcher.
natebosch added a commit that referenced this pull request Oct 4, 2019
See #90 (comment)

Merged streams forward events synchronously so we do know that
guarantees that events keep their order when forwarded. Since it's not
necessary to allow for ordering changes drop the `unorderedEquals`.

Also refactor to async/await from a `completion` matcher.
mosuem pushed a commit to dart-lang/core that referenced this pull request Oct 14, 2024
mosuem pushed a commit to dart-lang/core that referenced this pull request Oct 14, 2024
See dart-archive/async#90 (comment)

Merged streams forward events synchronously so we do know that
guarantees that events keep their order when forwarded. Since it's not
necessary to allow for ordering changes drop the `unorderedEquals`.

Also refactor to async/await from a `completion` matcher.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Development

Successfully merging this pull request may close these issues.

3 participants