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

Bringing our next branch up to date #2317

Merged
merged 33 commits into from
Jan 31, 2017
Merged

Bringing our next branch up to date #2317

merged 33 commits into from
Jan 31, 2017

Conversation

jayphelps
Copy link
Member

No description provided.

feloy and others added 30 commits December 23, 2016 18:47
combineLatest

lease enter the commit message for your changes. Lines starting
…if the catch subscription is di (#2271)

This is a non-breaking change to make track and dispose its subscription to the Observable returned
from the catch selector if the catch subscriber is disposed early.
When using a number interval, we must now use `sampleTime` instead of `sample`. This was not specified in the document.
* Change keyboard event in tutorial example

The `keypress` event is send before the value has been set on the input element : it always returns the last value of the element.
When 'keydown' is send, the value has already been set on the input; returning the actual value.

* Update basics.md

The KeyboardEvent (keydown, keypress, keyup) indicates just what's happening on a key. When you need to handle text input, use HTML5 input event instead. For example, if user inputs text from hand-writing system like tablet PC, key events may not be fired.
Align fromEventPattern behavior to RxJS v4
* chore(readme): Simplifes CDN usage directions

* chore(cdn): use rxjs package not reactivex/rxjs
* docs(operators): mergeScan

* docs(operators): toPromise

* docs(toPromise): Fix copy-paste mistake

* docs(mergeScan): `var` -> `const`. Use Finnish notation.
docs(operators): examples for catch operator
refactor(windowTime): clarify type definition of windowTime
* test(AsyncSubject): asyncsubject should not send complete event after error

* fix(AsynSubject): check if there is an error first

* test(AsyncSubject): asyncSubject should not send error event after complete

* fix(AsyncSubject): only pass error if asyncsubject is not completed
…ent down error channel (#2313)

- Fixes `Observable.create(fn)` and `new Observable(fn)` such that any error thrown in `fn` on subscription will be sent to the subscriber's error handler.
- Fixes a subject test that was relying on the errant behavior.

fixes #1833
…e` and `ColdObservable` instead of Observable (#2305)

Return `HotObservable` and `ColdObservable` instead of simply `Observable`, in order to give users access to subscriptions parameter
…servable's initializer function is the same.

- closes #2166
…plete, even if a hot notifier completes first. (#2209)

After notifier completes wait for source observable to complete instead
of ending stream immediately

Closes #2054
@jayphelps jayphelps merged commit 8af24dd into next Jan 31, 2017
@coveralls
Copy link

coveralls commented Jan 31, 2017

Coverage Status

Coverage increased (+0.006%) to 97.702% when pulling a77821b on master into f8ba77d on next.

@lock
Copy link

lock bot commented Jun 6, 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 6, 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.