nx-packaged icon indicating copy to clipboard operation
nx-packaged copied to clipboard

Published 20 hours ago • verified publisher icon ng-packagr

build: update rxjs to version ^7.0.0-beta

Open renovate[bot] opened this issue 6 years ago • 0 comments

This PR contains the following updates:

Package Type Update Change
rxjs (source) dependencies major ^6.4.0 -> ^7.0.0-beta

Release Notes

reactivex/rxjs

v7.0.0-beta.8

Compare Source

Bug Fixes
  • audit, auditTime: audit and auditTime emit last value after source completes (#​5799) (643bc85), closes #​5730
  • No longer allow invalid "Subscribable" type as valid observable source in from and others. (258dddd), closes #​4532
  • bindNodeCallback: ensure underlying function is not called twice during subscription (#​5780) (74aa4b2)
  • delay: Now properly handles Date and negative numbers (#​5719) (868c02b), closes #​5232
  • delayWhen: only deprecates when subscriptionDelay presents (#​5797) (43d1731)
  • every: index properly increments in predicate (5686f83)
  • firstValueFrom: now unsubscribes from source after first value is received (#​5813) (a321516), closes #​5811
  • from: objects that are thennable that happen to have a subscribe method will no longer error. (789d6e3)
  • fromEvent: now properly types JQuery event targets (b5aa15a)
  • mergeScan: no longer emits state again upon completion. (#​5805) (68c2894), closes #​5372
  • throttle: now supports synchronous duration selectors (55e953e), closes #​5658
  • throttle: trailing values will now emit after source completes (d5fd69c)
  • timeout: allows synchronous observable as a source (84c5c0b), closes #​5746
  • zip: zip now accepts an array of arguments like its counterparts (3123b67)
Code Refactoring
Features
BREAKING CHANGES
  • mergeScan: mergeScan will no longer emit its inner state again upon completion.
  • pairs: pairs will no longer function in IE without a polyfill for Object.entries. pairs itself is also deprecated in favor of users just using from(Object.entries(obj)).
  • zip: Zipping a single array will now have a different result. This is an extreme corner-case, because it is very unlikely that anyone would want to zip an array with nothing at all. The workaround would be to wrap the array in another array zip([[1,2,3]]). But again, that's pretty weird.
  • count: No longer passes source observable as a third argument to the predicate. That feature was rarely used, and of limited value. The workaround is to simply close over the source inside of the function if you need to access it in there.

v7.0.0-beta.7

Compare Source

Bug Fixes
  • multicast: and other publish variants will handle errors thrown in a selector appropriately (bde8eda)
Code Refactoring
  • tap: reduce the size of the implementation (1222d5a)
  • Subscriber: Massively untangle Subscriber and SafeSubscriber (07902ca)
BREAKING CHANGES
  • Subscriber: new Subscriber no longer takes 0-3 arguments. To create a Subscriber with 0-3 arguments, use Subscriber.create. However, please note that there is little to no reason that you should be creating Subscriber references directly, and Subscriber.create and new Subscriber are both deprecated.

v7.0.0-beta.6

Compare Source

Bug Fixes
Code Refactoring
  • Massive Size Reduction: reduced the size of all operator implementations as well as other utilities and types (#​5729) (4d3fc23)
Features
  • onUnhandledError: configuration point added for unhandled errors (#​5681) (3485dd5)
  • skipLast: counts zero or less will mirror the source (02e113b)
BREAKING CHANGES
  • skipLast: skipLast will no longer error when passed a negative number, rather it will simply return the source, as though 0 was passed.
  • map: thisArg will now default to undefined. The previous default of MapSubscriber never made any sense. This will only affect code that calls map with a function and references this like so: source.pipe(map(function () { console.log(this); })). There wasn't anything useful about doing this, so the breakage is expected to be very minimal. If anything we're no longer leaking an implementation detail.
  • onUnhandledError: Errors that occur during setup of an observable subscription after the subscription has emitted an error or completed will now throw in their own call stack. Before it would call console.warn. This is potentially breaking in edge cases for node applications, which may be configured to terminate for unhandled exceptions. In the unlikely event this affects you, you can configure the behavior to console.warn in the new configuration setting like so: import { config } from 'rxjs'; config.onUnhandledError = (err) => console.warn(err);

v7.0.0-beta.5

Compare Source

Bug Fixes
  • ajax: Allow XHR to perform body serialization and set content-type where possible (d8657ed), closes #​2837
  • ajax: Do not mutate headers passed as arguments (0d66ba4), closes #​2801
  • bindCallback: now emits errors that happen after callback (2bddd31)
  • bindNodeCallback: now emits errors that happen after callback (edc28cf)
  • buffer: Ensure notifier is subscribed after source (#​5654) (c088b0e), closes #​2195 #​1754
  • catchError: ensure proper handling of async return for synchronous source error handling (#​5627) (1b29d4b), closes #​5115
  • catchError: inner synchronous observables will properly terminate (#​5655) (d3fd2fb)
  • errors: Custom RxJS errors now all have a call stack (#​5686) (9bb046c), closes #​4250
  • onErrorResumeNext: observables always finalized before moving to next source (#​5650) (ff68ad2)
  • package.json: change homepage setting to official docs site. (#​5669) (e57c402)
  • repeat: Ensure teardown happens between repeated synchronous obs… (#​5620) (0ca8a65)
  • repeatWhen: Ensure teardown happens between repeat subscriptions (#​5625) (98356f4)
  • retry: Ensure teardown happens before resubscription with synchronous observables (6f90597), closes #​5620
  • retryWhen: Ensure subscription tears down between retries (#​5623) (6752af7)
  • throttleTime: ensure the spacing between throttles is always at least the throttled amount (#​5687) (ea84fc4), closes #​3712 #​4864 #​2727 #​4727 #​4429
  • zip: zip operators and functions are now able to zip all iterable sources (#​5688) (02c3a1b), closes #​4304
  • switchMap and exhaustMap behave correctly with re-entrant code. (c289688)
  • webSocket: close websocket connection attempt on unsubscribe (e1a671c), closes #​4446
Code Refactoring
  • ajax: Use simple Observable (17b9add)
  • Subscriber: remove _unsubscribeAndRecycle (d879c3f)
  • VirtualTimeScheduler: remove sortActions from public API (#​5657) (a468f88)
Features
  • combineLatest: add N-args signature for observable inputs (#​5488) (fcc47e7)
  • Subscription: add no longer returns unnecessary Subscription reference (#​5656) (4de604e)
  • Subscription: remove will now remove any teardown by reference (#​5659) (1531152)
  • throwError: now accepts a factory to create the error (#​5647) (dad270a), closes #​5617
  • useDeprecatedNextContext: Puts deprecated next context behavior behind a flag (dfdef5d)
  • support schedulers within run (#​5619) (c63de0d)
Performance Improvements
  • SafeSubscriber: avoid using Object.create (40a9e77)
BREAKING CHANGES

  • ajax:

    • ajax body serialization will now use default XHR behavior in all cases. If the body is a Blob, ArrayBuffer, any array buffer view (like a byte sequence, e.g. Uint8Array, etc), FormData, URLSearchParams, string, or ReadableStream, default handling is use. If the body is otherwise typeof "object", then it will be converted to JSON via JSON.stringify, and the Content-Type header will be set to application/json;charset=utf-8. All other types will emit an error.
    • The Content-Type header passed to ajax configuration no longer has any effect on the serialization behavior of the AJAX request.
    • For TypeScript users, AjaxRequest is no longer the type that should be explicitly used to create an ajax. It is now AjaxConfig, although the two types are compatible, only AjaxConfig has progressSubscriber and createXHR.

  • zip: zip operators will no longer iterate provided iterables "as needed", instead the iterables will be treated as push-streams just like they would be everywhere else in RxJS. This means that passing an endless iterable will result in the thread locking up, as it will endlessly try to read from that iterable. This puts us in-line with all other Rx implementations. To work around this, it is probably best to use map or some combination of map and zip. For example, zip(source$, iterator) could be source$.pipe(map(value => [value, iterator.next().value])).

  • Subscription: add no longer returns an unnecessary Subscription reference. This was done to prevent confusion caused by a legacy behavior. You can now add and remove functions and Subscriptions as teardowns to and from a Subscription using add and remove directly. Before this, remove only accepted subscriptions.

  • RxJS Error types Tests that are written with naive expectations against errors may fail now that errors have a proper stack property. In some testing frameworks, a deep equality check on two error instances will check the values in stack, which could be different.

  • Undocumented Behaviors/APIs Removed:

    • unsubscribe no longer available via the this context of observer functions. To reenable, set config.useDeprecatedNextContext = true on the rxjs config found at import { config } from 'rxjs';. Note that enabling this will result in a performance penalty for all consumer subscriptions.
    • Leaked implementation detail _unsubscribeAndRecycle of Subscriber has been removed. Just use new Subscription objects
    • Removed an undocumented behavior where passing a negative count argument to retry would result in an observable that repeats forever.
    • An undocumented behavior where passing a negative count argument to repeat would result in an observable that repeats forever.
    • The static sortActions method on VirtualTimeScheduler is no longer publicly exposed by our TS types.

  • throwError: In an extreme corner case for usage, throwError is no longer able to emit a function as an error directly. If you need to push a function as an error, you will have to use the factory function to return the function like so: throwError(() => functionToEmit), in other words throwError(() => () => console.log('called later')).

v7.0.0-beta.4

Compare Source

Bug Fixes
  • ajax: Partial observers passed to progressSubscriber will no longer error (25d279f)
  • ajax: Unparsable responses will no longer prevent full AjaxError from being thrown (605ee55)
  • animationFrames: emit the timestamp from the rAF's callback (#​5438) (c980ae6)
  • Ensure unsubscriptions/teardowns on internal subscribers are idempotent (#​5465) (3e39749), closes #​5464
  • timeout: defer error creation until timeout occurs (#​5497) (3be9840), closes #​5491
Code Refactoring
  • ajax: Drop support for IE10 and lower (0eaadd6)
  • Observable: Update property and method types (#​5572) (144b626)
Features
BREAKING CHANGES
  • ajax: In an extreme corner-case... If an error occurs, the responseType is "json", we're in IE, and the responseType is not valid JSON, the ajax observable will no longer emit a syntax error, rather it will emit a full AjaxError with more details.
  • ajax: Ajax implementation drops support for IE10 and lower. This puts us in-line with other implementations and helps clean up code in this area
  • Observable: lift no longer exposed. It was NEVER documented that end users of the library should be creating operators using lift. Lift has a variety of issues and was always an internal implementation detail of rxjs that might have been used by a few power users in the early days when it had the most value. The value of lift, originally, was that subclassed Observables would compose through all operators that implemented lift. The reality is that feature is not widely known, used, or supported, and it was never documented as it was very experimental when it was first added. Until the end of v7, lift will remain on Observable. Standard JavaScript users will notice no difference. However, TypeScript users might see complaints about lift not being a member of observable. To workaround this issue there are two things you can do: 1. Rewrite your operators as outlined in the documentation, such that they return new Observable. or 2. cast your observable as any and access lift that way. Method 1 is recommended if you do not want things to break when we move to version 8.

v7.0.0-beta.3

Compare Source

Bug Fixes
Code Refactoring
  • perf: Reduce memory pressure by no longer retaining outer values across the majority of operators. (#​5610) (bff1827)
  • Observable: Update property and method types (#​5572) (144b626)
Features
BREAKING CHANGES
  • Observable: lift no longer exposed. It was never documented that end users of the library should be creating operators using lift. Lift has a variety of issues and was always an internal implementation detail of rxjs that might have been used by a few power users in the early days when it had the most value. The value of lift, originally, was that subclassed Observables would compose through all operators that implemented lift. The reality is that feature is not widely known, used, or supported, and it was never documented as it was very experimental when it was first added. Until the end of v7, lift will remain on Observable. Standard JavaScript users will notice no difference. However, TypeScript users might see complaints about lift not being a member of observable. To workaround this issue there are two things you can do: 1. Rewrite your operators as outlined in the documentation, such that they return new Observable. or 2. cast your observable as any and access lift that way. It is recommended that operators be implemented in terms of functions that return (sourcc: Observable<T>) => new Observable<R>(...), per the documentation/guide.

v7.0.0-beta.2

Compare Source

Bug Fixes
  • dependencies: Move accidental dependency on typedoc to dev-dependencies. (#​5566) (45702bf)

v7.0.0-beta.1

Compare Source

Bug Fixes
Features
BREAKING CHANGES

  • Notification.createNext(undefined) will no longer return the exact same reference everytime.

  • Type signatures tightened up around Notification and dematerialize, may uncover issues with invalid types passed to those operators.

  • Experimental support for for await as been removed. Use https://github.com/benlesh/rxjs-for-await instead.

  • defer no longer allows factories to return void or undefined. All factories passed to defer must return a proper ObservableInput, such as Observable, Promise, et al. To get the same behavior as you may have relied on previously, return EMPTY or return of() from the factory.

  • single operator will now throw for scenarios where values coming in are either not present, or do not match the provided predicate. Error types have thrown have also been updated, please check documentation for changes.

  • take and will now throw runtime error for arguments that are negative or NaN, this includes non-TS calls like take().

  • takeLast now has runtime assertions that throw TypeErrors for invalid arguments. Calling takeLast without arguments or with an argument that is NaN will throw a TypeError

  • ReplaySubject no longer schedules emissions when a scheduler is provided. If you need that behavior, please compose in observeOn using pipe, for example: new ReplaySubject(2, 3000).pipe(observeOn(asap))

  • timestamp operator accepts a TimestampProvider, which is any object with a now method that returns a number. This means pulling in less code for the use of the timestamp operator. This may cause issues with TestScheduler run mode. (Issue here: ReactiveX#​5553)

v7.0.0-beta.0

Compare Source

Bug Fixes
Features
  • add lastValueFrom and firstValueFrom methods (#​5295) (e69b765)
  • RxJS now supports first-class interop with AsyncIterables (4fa9d01)
  • combineLatestWith: adds combineLatestWith - renamed legacy combineLatest operator (#​5251) (6d7b146)
  • retry: add config to reset error count on successful emission (#​5280) (ab6e9fc)
  • zipWith: add zipWith which is just a rename of legacy zip operator (#​5249) (86b6a27)
BREAKING CHANGES
  • startWith: startWith will return incorrect types when called with more than 7 arguments and a scheduler. Passing scheduler to startWith is deprecated
  • toPromise: toPromise return type now returns T | undefined in TypeScript, which is correct, but may break builds.

v7.0.0-alpha.1

Compare Source

Bug Fixes
  • chain subscriptions from observables that belong to other instances of RxJS (e.g. in node_modules) (#​5059) (d7f7078)
  • clear subscription on shareReplay completion (#​5044) (35e600f), closes #​5034
  • closure: Annotate next() for ReplaySubject (#​5088) (8687fbd)
  • closure: static prop frameTimeFactor being collapsed when compiled with closure. (39872c9)
  • docs: remove repetitive op3() in example (#​5043) (e17df33)
  • filter: Fix overload order for filter to support inferring the generic type (#​5024) (8255365)
  • fromFetch: passing already aborted signal to init aborts fetch (0e4849a)
Features

v7.0.0-alpha.0

Compare Source

Bug Fixes
Features
BREAKING CHANGES
  • concat: Generic signature changed. Recommend not explicitly passing generics, just let inference do its job. If you must, cast with as.
  • of: Generic signature changed, do not specify generics, allow them to be inferred or use as
  • of: Use with more than 9 arguments, where the last argument is a SchedulerLike may result in the wrong type which includes the SchedulerLike, even though the run time implementation does not support that. Developers should be using scheduled instead
  • TS: RxJS requires TS 3.5
  • rxjs-compat: rxjs/Rx is no longer a valid import site.
  • rxjs-compat: rxjs-compat is not published for v7 (yet)
  • race: race() will no longer subscribe to subsequent observables if a provided source synchronously errors or completes. This means side effects that might have occurred during subscription in those rare cases will no longer occur.

6.5.3 (2019-09-03)

Bug Fixes

6.5.2 (2019-05-10)

Bug Fixes

6.5.1 (2019-04-23)

Bug Fixes

Renovate configuration

:date: Schedule: At any time (no schedule defined).

:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.

:recycle: Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

:no_bell: Ignore: Close this PR and you won't be reminded about this update again.

  • [ ] If you want to rebase/retry this PR, check this box

This PR has been generated by WhiteSource Renovate. View repository job log here.

renovate[bot] avatar Oct 01 '19 05:10 renovate[bot]