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.

Sign up for GitHub

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

2.x: Fix copy-paste errors in SingleSubject JavaDoc #5834

Merged
merged 1 commit into from
Feb 2, 2018
Merged

2.x: Fix copy-paste errors in SingleSubject JavaDoc #5834

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions src/main/java/io/reactivex/subjects/SingleSubject.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,8 +34,8 @@
* as parameters to {@link #onSuccess(Object)} and {@link #onError(Throwable)}. Such calls will result in a
* {@link NullPointerException} being thrown and the subject's state is not changed.
* <p>
* Since a {@code SingleSubject} is a {@link io.reactivex.Maybe}, calling {@code onSuccess}, {@code onError}
* or {@code onComplete} will move this {@code SingleSubject} into its terminal state atomically.
* Since a {@code SingleSubject} is a {@link io.reactivex.Single}, calling {@code onSuccess} or {@code onError}
* will move this {@code SingleSubject} into its terminal state atomically.
* <p>
* All methods are thread safe. Calling {@link #onSuccess(Object)} multiple
* times has no effect. Calling {@link #onError(Throwable)} multiple times relays the {@code Throwable} to
Expand All @@ -55,8 +55,8 @@
* <dl>
* <dt><b>Scheduler:</b></dt>
* <dd>{@code SingleSubject} does not operate by default on a particular {@link io.reactivex.Scheduler} and
* the {@code SingleObserver}s get notified on the thread where the terminating {@code onSuccess}, {@code onError}
* or {@code onComplete} methods were invoked.</dd>
* the {@code SingleObserver}s get notified on the thread where the terminating {@code onSuccess} or {@code onError}
* methods were invoked.</dd>
* <dt><b>Error handling:</b></dt>
* <dd>When the {@link #onError(Throwable)} is called, the {@code SingleSubject} enters into a terminal state
* and emits the same {@code Throwable} instance to the last set of {@code SingleObserver}s. During this emission,
Expand Down