Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(share): add the share operator #440

Merged
merged 1 commit into from
Oct 3, 2015
Merged

feat(share): add the share operator #440

merged 1 commit into from
Oct 3, 2015

Conversation

benlesh
Copy link
Member

@benlesh benlesh commented Oct 1, 2015

closes #439

@staltz
Copy link
Member

staltz commented Oct 2, 2015

I would merge 👍


expect(subscriptionCount).toBe(1);
});

Copy link
Member

Choose a reason for hiding this comment

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

Should we also have a marble test where e1 is a cold Observable to make sense applying share on it? Also the case of multiple subscribers to a was-cold shared Observable makes a lot of sense to have a subscribe-and-unsubscribe marble diagram test that we mentioned in #428.

Copy link
Member Author

Choose a reason for hiding this comment

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

Probably

@benlesh benlesh merged commit c36f2be into ReactiveX:master Oct 3, 2015
@benlesh benlesh deleted the share branch April 27, 2016 17:20
@lock
Copy link

lock bot commented Jun 7, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jun 7, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Implement share operator
2 participants