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

Proposal: standardized Subject state-peeking methods. #2883

Merged
merged 1 commit into from
Apr 29, 2015

Conversation

akarnokd
Copy link
Member

This PR modifies the Subject class to host the union of the state-peeking methods of the various Subject implementations and fixes the inconsistent behavior of ReplaySubject.getValues(T[]).

The changes enable the SerializedSubject to relay such state-peeking method calls into the wrapped subject and allows future Subject wrappers to do the same (#2458).

@benjchristensen
Copy link
Member

Seems to make sense. The additions to Subject all should be non-breaking.

@benjchristensen
Copy link
Member

Due to the Experimental marking of these I'm being a little less stringent in discussing the addition to public APIs, but it seems to me that the precedent set on the BehaviorSubject shows the value of these methods. Additionally, Subjects are the stateful, side-effecting types and these methods seem to make sense for them.

benjchristensen added a commit that referenced this pull request Apr 29, 2015
Proposal: standardized Subject state-peeking methods.
@benjchristensen benjchristensen merged commit d3d15b9 into ReactiveX:1.x Apr 29, 2015
@akarnokd akarnokd deleted the ExtendedSubjectAPI branch April 29, 2015 06:31
@benjchristensen benjchristensen mentioned this pull request Apr 30, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants