taskninja 1.1.5 → 1.1.6

package/src/node_modules/rxjs/src/internal/observable/from.ts

@@ -1,104 +0,0 @@
-import { Observable } from '../Observable';
-import { ObservableInput, SchedulerLike, ObservedValueOf } from '../types';
-import { scheduled } from '../scheduled/scheduled';
-import { innerFrom } from './innerFrom';
-
-export function from<O extends ObservableInput<any>>(input: O): Observable<ObservedValueOf<O>>;
-/** @deprecated The `scheduler` parameter will be removed in v8. Use `scheduled`. Details: https://rxjs.dev/deprecations/scheduler-argument */
-export function from<O extends ObservableInput<any>>(input: O, scheduler: SchedulerLike | undefined): Observable<ObservedValueOf<O>>;
-
-/**
- * Creates an Observable from an Array, an array-like object, a Promise, an iterable object, or an Observable-like object.
- *
- * <span class="informal">Converts almost anything to an Observable.</span>
- *
- * ![](from.png)
- *
- * `from` converts various other objects and data types into Observables. It also converts a Promise, an array-like, or an
- * <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Iteration_protocols#iterable" target="_blank">iterable</a>
- * object into an Observable that emits the items in that promise, array, or iterable. A String, in this context, is treated
- * as an array of characters. Observable-like objects (contains a function named with the ES2015 Symbol for Observable) can also be
- * converted through this operator.
- *
- * ## Examples
- *
- * Converts an array to an Observable
- *
- * ```ts
- * import { from } from 'rxjs';
- *
- * const array = [10, 20, 30];
- * const result = from(array);
- *
- * result.subscribe(x => console.log(x));
- *
- * // Logs:
- * // 10
- * // 20
- * // 30
- * ```
- *
- * Convert an infinite iterable (from a generator) to an Observable
- *
- * ```ts
- * import { from, take } from 'rxjs';
- *
- * function* generateDoubles(seed) {
- *    let i = seed;
- *    while (true) {
- *      yield i;
- *      i = 2 * i; // double it
- *    }
- * }
- *
- * const iterator = generateDoubles(3);
- * const result = from(iterator).pipe(take(10));
- *
- * result.subscribe(x => console.log(x));
- *
- * // Logs:
- * // 3
- * // 6
- * // 12
- * // 24
- * // 48
- * // 96
- * // 192
- * // 384
- * // 768
- * // 1536
- * ```
- *
- * With `asyncScheduler`
- *
- * ```ts
- * import { from, asyncScheduler } from 'rxjs';
- *
- * console.log('start');
- *
- * const array = [10, 20, 30];
- * const result = from(array, asyncScheduler);
- *
- * result.subscribe(x => console.log(x));
- *
- * console.log('end');
- *
- * // Logs:
- * // 'start'
- * // 'end'
- * // 10
- * // 20
- * // 30
- * ```
- *
- * @see {@link fromEvent}
- * @see {@link fromEventPattern}
- *
- * @param input A subscription object, a Promise, an Observable-like,
- * an Array, an iterable, or an array-like object to be converted.
- * @param scheduler An optional {@link SchedulerLike} on which to schedule the emission of values.
- * @return An Observable converted from {@link ObservableInput}.
- */
-export function from<T>(input: ObservableInput<T>, scheduler?: SchedulerLike): Observable<T> {
-  return scheduler ? scheduled(input, scheduler) : innerFrom(input);
-}

package/src/node_modules/rxjs/src/internal/observable/fromEvent.ts

@@ -1,339 +0,0 @@
-import { innerFrom } from '../observable/innerFrom';
-import { Observable } from '../Observable';
-import { mergeMap } from '../operators/mergeMap';
-import { isArrayLike } from '../util/isArrayLike';
-import { isFunction } from '../util/isFunction';
-import { mapOneOrManyArgs } from '../util/mapOneOrManyArgs';
-
-// These constants are used to create handler registry functions using array mapping below.
-const nodeEventEmitterMethods = ['addListener', 'removeListener'] as const;
-const eventTargetMethods = ['addEventListener', 'removeEventListener'] as const;
-const jqueryMethods = ['on', 'off'] as const;
-
-export interface NodeStyleEventEmitter {
-  addListener(eventName: string | symbol, handler: NodeEventHandler): this;
-  removeListener(eventName: string | symbol, handler: NodeEventHandler): this;
-}
-
-export type NodeEventHandler = (...args: any[]) => void;
-
-// For APIs that implement `addListener` and `removeListener` methods that may
-// not use the same arguments or return EventEmitter values
-// such as React Native
-export interface NodeCompatibleEventEmitter {
-  addListener(eventName: string, handler: NodeEventHandler): void | {};
-  removeListener(eventName: string, handler: NodeEventHandler): void | {};
-}
-
-// Use handler types like those in @types/jquery. See:
-// https://github.com/DefinitelyTyped/DefinitelyTyped/blob/847731ba1d7fa6db6b911c0e43aa0afe596e7723/types/jquery/misc.d.ts#L6395
-export interface JQueryStyleEventEmitter<TContext, T> {
-  on(eventName: string, handler: (this: TContext, t: T, ...args: any[]) => any): void;
-  off(eventName: string, handler: (this: TContext, t: T, ...args: any[]) => any): void;
-}
-
-export interface EventListenerObject<E> {
-  handleEvent(evt: E): void;
-}
-
-export interface HasEventTargetAddRemove<E> {
-  addEventListener(
-    type: string,
-    listener: ((evt: E) => void) | EventListenerObject<E> | null,
-    options?: boolean | AddEventListenerOptions
-  ): void;
-  removeEventListener(
-    type: string,
-    listener: ((evt: E) => void) | EventListenerObject<E> | null,
-    options?: EventListenerOptions | boolean
-  ): void;
-}
-
-export interface EventListenerOptions {
-  capture?: boolean;
-  passive?: boolean;
-  once?: boolean;
-}
-
-export interface AddEventListenerOptions extends EventListenerOptions {
-  once?: boolean;
-  passive?: boolean;
-}
-
-export function fromEvent<T>(target: HasEventTargetAddRemove<T> | ArrayLike<HasEventTargetAddRemove<T>>, eventName: string): Observable<T>;
-export function fromEvent<T, R>(
-  target: HasEventTargetAddRemove<T> | ArrayLike<HasEventTargetAddRemove<T>>,
-  eventName: string,
-  resultSelector: (event: T) => R
-): Observable<R>;
-export function fromEvent<T>(
-  target: HasEventTargetAddRemove<T> | ArrayLike<HasEventTargetAddRemove<T>>,
-  eventName: string,
-  options: EventListenerOptions
-): Observable<T>;
-export function fromEvent<T, R>(
-  target: HasEventTargetAddRemove<T> | ArrayLike<HasEventTargetAddRemove<T>>,
-  eventName: string,
-  options: EventListenerOptions,
-  resultSelector: (event: T) => R
-): Observable<R>;
-
-export function fromEvent(target: NodeStyleEventEmitter | ArrayLike<NodeStyleEventEmitter>, eventName: string): Observable<unknown>;
-/** @deprecated Do not specify explicit type parameters. Signatures with type parameters that cannot be inferred will be removed in v8. */
-export function fromEvent<T>(target: NodeStyleEventEmitter | ArrayLike<NodeStyleEventEmitter>, eventName: string): Observable<T>;
-export function fromEvent<R>(
-  target: NodeStyleEventEmitter | ArrayLike<NodeStyleEventEmitter>,
-  eventName: string,
-  resultSelector: (...args: any[]) => R
-): Observable<R>;
-
-export function fromEvent(
-  target: NodeCompatibleEventEmitter | ArrayLike<NodeCompatibleEventEmitter>,
-  eventName: string
-): Observable<unknown>;
-/** @deprecated Do not specify explicit type parameters. Signatures with type parameters that cannot be inferred will be removed in v8. */
-export function fromEvent<T>(target: NodeCompatibleEventEmitter | ArrayLike<NodeCompatibleEventEmitter>, eventName: string): Observable<T>;
-export function fromEvent<R>(
-  target: NodeCompatibleEventEmitter | ArrayLike<NodeCompatibleEventEmitter>,
-  eventName: string,
-  resultSelector: (...args: any[]) => R
-): Observable<R>;
-
-export function fromEvent<T>(
-  target: JQueryStyleEventEmitter<any, T> | ArrayLike<JQueryStyleEventEmitter<any, T>>,
-  eventName: string
-): Observable<T>;
-export function fromEvent<T, R>(
-  target: JQueryStyleEventEmitter<any, T> | ArrayLike<JQueryStyleEventEmitter<any, T>>,
-  eventName: string,
-  resultSelector: (value: T, ...args: any[]) => R
-): Observable<R>;
-
-/**
- * Creates an Observable that emits events of a specific type coming from the
- * given event target.
- *
- * <span class="informal">Creates an Observable from DOM events, or Node.js
- * EventEmitter events or others.</span>
- *
- * ![](fromEvent.png)
- *
- * `fromEvent` accepts as a first argument event target, which is an object with methods
- * for registering event handler functions. As a second argument it takes string that indicates
- * type of event we want to listen for. `fromEvent` supports selected types of event targets,
- * which are described in detail below. If your event target does not match any of the ones listed,
- * you should use {@link fromEventPattern}, which can be used on arbitrary APIs.
- * When it comes to APIs supported by `fromEvent`, their methods for adding and removing event
- * handler functions have different names, but they all accept a string describing event type
- * and function itself, which will be called whenever said event happens.
- *
- * Every time resulting Observable is subscribed, event handler function will be registered
- * to event target on given event type. When that event fires, value
- * passed as a first argument to registered function will be emitted by output Observable.
- * When Observable is unsubscribed, function will be unregistered from event target.
- *
- * Note that if event target calls registered function with more than one argument, second
- * and following arguments will not appear in resulting stream. In order to get access to them,
- * you can pass to `fromEvent` optional project function, which will be called with all arguments
- * passed to event handler. Output Observable will then emit value returned by project function,
- * instead of the usual value.
- *
- * Remember that event targets listed below are checked via duck typing. It means that
- * no matter what kind of object you have and no matter what environment you work in,
- * you can safely use `fromEvent` on that object if it exposes described methods (provided
- * of course they behave as was described above). So for example if Node.js library exposes
- * event target which has the same method names as DOM EventTarget, `fromEvent` is still
- * a good choice.
- *
- * If the API you use is more callback then event handler oriented (subscribed
- * callback function fires only once and thus there is no need to manually
- * unregister it), you should use {@link bindCallback} or {@link bindNodeCallback}
- * instead.
- *
- * `fromEvent` supports following types of event targets:
- *
- * **DOM EventTarget**
- *
- * This is an object with `addEventListener` and `removeEventListener` methods.
- *
- * In the browser, `addEventListener` accepts - apart from event type string and event
- * handler function arguments - optional third parameter, which is either an object or boolean,
- * both used for additional configuration how and when passed function will be called. When
- * `fromEvent` is used with event target of that type, you can provide this values
- * as third parameter as well.
- *
- * **Node.js EventEmitter**
- *
- * An object with `addListener` and `removeListener` methods.
- *
- * **JQuery-style event target**
- *
- * An object with `on` and `off` methods
- *
- * **DOM NodeList**
- *
- * List of DOM Nodes, returned for example by `document.querySelectorAll` or `Node.childNodes`.
- *
- * Although this collection is not event target in itself, `fromEvent` will iterate over all Nodes
- * it contains and install event handler function in every of them. When returned Observable
- * is unsubscribed, function will be removed from all Nodes.
- *
- * **DOM HtmlCollection**
- *
- * Just as in case of NodeList it is a collection of DOM nodes. Here as well event handler function is
- * installed and removed in each of elements.
- *
- *
- * ## Examples
- *
- * Emit clicks happening on the DOM document
- *
- * ```ts
- * import { fromEvent } from 'rxjs';
- *
- * const clicks = fromEvent(document, 'click');
- * clicks.subscribe(x => console.log(x));
- *
- * // Results in:
- * // MouseEvent object logged to console every time a click
- * // occurs on the document.
- * ```
- *
- * Use `addEventListener` with capture option
- *
- * ```ts
- * import { fromEvent } from 'rxjs';
- *
- * const div = document.createElement('div');
- * div.style.cssText = 'width: 200px; height: 200px; background: #09c;';
- * document.body.appendChild(div);
- *
- * // note optional configuration parameter which will be passed to addEventListener
- * const clicksInDocument = fromEvent(document, 'click', { capture: true });
- * const clicksInDiv = fromEvent(div, 'click');
- *
- * clicksInDocument.subscribe(() => console.log('document'));
- * clicksInDiv.subscribe(() => console.log('div'));
- *
- * // By default events bubble UP in DOM tree, so normally
- * // when we would click on div in document
- * // "div" would be logged first and then "document".
- * // Since we specified optional `capture` option, document
- * // will catch event when it goes DOWN DOM tree, so console
- * // will log "document" and then "div".
- * ```
- *
- * @see {@link bindCallback}
- * @see {@link bindNodeCallback}
- * @see {@link fromEventPattern}
- *
- * @param target The DOM EventTarget, Node.js EventEmitter, JQuery-like event target,
- * NodeList or HTMLCollection to attach the event handler to.
- * @param eventName The event name of interest, being emitted by the `target`.
- * @param options Options to pass through to the underlying `addListener`,
- * `addEventListener` or `on` functions.
- * @param resultSelector A mapping function used to transform events. It takes the
- * arguments from the event handler and should return a single value.
- * @return An Observable emitting events registered through `target`'s
- * listener handlers.
- */
-export function fromEvent<T>(
-  target: any,
-  eventName: string,
-  options?: EventListenerOptions | ((...args: any[]) => T),
-  resultSelector?: (...args: any[]) => T
-): Observable<T> {
-  if (isFunction(options)) {
-    resultSelector = options;
-    options = undefined;
-  }
-  if (resultSelector) {
-    return fromEvent<T>(target, eventName, options as EventListenerOptions).pipe(mapOneOrManyArgs(resultSelector));
-  }
-
-  // Figure out our add and remove methods. In order to do this,
-  // we are going to analyze the target in a preferred order, if
-  // the target matches a given signature, we take the two "add" and "remove"
-  // method names and apply them to a map to create opposite versions of the
-  // same function. This is because they all operate in duplicate pairs,
-  // `addListener(name, handler)`, `removeListener(name, handler)`, for example.
-  // The call only differs by method name, as to whether or not you're adding or removing.
-  const [add, remove] =
-    // If it is an EventTarget, we need to use a slightly different method than the other two patterns.
-    isEventTarget(target)
-      ? eventTargetMethods.map((methodName) => (handler: any) => target[methodName](eventName, handler, options as EventListenerOptions))
-      : // In all other cases, the call pattern is identical with the exception of the method names.
-      isNodeStyleEventEmitter(target)
-      ? nodeEventEmitterMethods.map(toCommonHandlerRegistry(target, eventName))
-      : isJQueryStyleEventEmitter(target)
-      ? jqueryMethods.map(toCommonHandlerRegistry(target, eventName))
-      : [];
-
-  // If add is falsy, it's because we didn't match a pattern above.
-  // Check to see if it is an ArrayLike, because if it is, we want to
-  // try to apply fromEvent to all of it's items. We do this check last,
-  // because there are may be some types that are both ArrayLike *and* implement
-  // event registry points, and we'd rather delegate to that when possible.
-  if (!add) {
-    if (isArrayLike(target)) {
-      return mergeMap((subTarget: any) => fromEvent(subTarget, eventName, options as EventListenerOptions))(
-        innerFrom(target)
-      ) as Observable<T>;
-    }
-  }
-
-  // If add is falsy and we made it here, it's because we didn't
-  // match any valid target objects above.
-  if (!add) {
-    throw new TypeError('Invalid event target');
-  }
-
-  return new Observable<T>((subscriber) => {
-    // The handler we are going to register. Forwards the event object, by itself, or
-    // an array of arguments to the event handler, if there is more than one argument,
-    // to the consumer.
-    const handler = (...args: any[]) => subscriber.next(1 < args.length ? args : args[0]);
-    // Do the work of adding the handler to the target.
-    add(handler);
-    // When we finalize, we want to remove the handler and free up memory.
-    return () => remove!(handler);
-  });
-}
-
-/**
- * Used to create `add` and `remove` functions to register and unregister event handlers
- * from a target in the most common handler pattern, where there are only two arguments.
- * (e.g.  `on(name, fn)`, `off(name, fn)`, `addListener(name, fn)`, or `removeListener(name, fn)`)
- * @param target The target we're calling methods on
- * @param eventName The event name for the event we're creating register or unregister functions for
- */
-function toCommonHandlerRegistry(target: any, eventName: string) {
-  return (methodName: string) => (handler: any) => target[methodName](eventName, handler);
-}
-
-/**
- * Checks to see if the target implements the required node-style EventEmitter methods
- * for adding and removing event handlers.
- * @param target the object to check
- */
-function isNodeStyleEventEmitter(target: any): target is NodeStyleEventEmitter {
-  return isFunction(target.addListener) && isFunction(target.removeListener);
-}
-
-/**
- * Checks to see if the target implements the required jQuery-style EventEmitter methods
- * for adding and removing event handlers.
- * @param target the object to check
- */
-function isJQueryStyleEventEmitter(target: any): target is JQueryStyleEventEmitter<any, any> {
-  return isFunction(target.on) && isFunction(target.off);
-}
-
-/**
- * Checks to see if the target implements the required EventTarget methods
- * for adding and removing event handlers.
- * @param target the object to check
- */
-function isEventTarget(target: any): target is HasEventTargetAddRemove<any> {
-  return isFunction(target.addEventListener) && isFunction(target.removeEventListener);
-}

package/src/node_modules/rxjs/src/internal/observable/fromEventPattern.ts

@@ -1,152 +0,0 @@
-import { Observable } from '../Observable';
-import { isFunction } from '../util/isFunction';
-import { NodeEventHandler } from './fromEvent';
-import { mapOneOrManyArgs } from '../util/mapOneOrManyArgs';
-
-/* tslint:disable:max-line-length */
-export function fromEventPattern<T>(
-  addHandler: (handler: NodeEventHandler) => any,
-  removeHandler?: (handler: NodeEventHandler, signal?: any) => void
-): Observable<T>;
-export function fromEventPattern<T>(
-  addHandler: (handler: NodeEventHandler) => any,
-  removeHandler?: (handler: NodeEventHandler, signal?: any) => void,
-  resultSelector?: (...args: any[]) => T
-): Observable<T>;
-/* tslint:enable:max-line-length */
-
-/**
- * Creates an Observable from an arbitrary API for registering event handlers.
- *
- * <span class="informal">When that method for adding event handler was something {@link fromEvent}
- * was not prepared for.</span>
- *
- * ![](fromEventPattern.png)
- *
- * `fromEventPattern` allows you to convert into an Observable any API that supports registering handler functions
- * for events. It is similar to {@link fromEvent}, but far
- * more flexible. In fact, all use cases of {@link fromEvent} could be easily handled by
- * `fromEventPattern` (although in slightly more verbose way).
- *
- * This operator accepts as a first argument an `addHandler` function, which will be injected with
- * handler parameter. That handler is actually an event handler function that you now can pass
- * to API expecting it. `addHandler` will be called whenever Observable
- * returned by the operator is subscribed, so registering handler in API will not
- * necessarily happen when `fromEventPattern` is called.
- *
- * After registration, every time an event that we listen to happens,
- * Observable returned by `fromEventPattern` will emit value that event handler
- * function was called with. Note that if event handler was called with more
- * than one argument, second and following arguments will not appear in the Observable.
- *
- * If API you are using allows to unregister event handlers as well, you can pass to `fromEventPattern`
- * another function - `removeHandler` - as a second parameter. It will be injected
- * with the same handler function as before, which now you can use to unregister
- * it from the API. `removeHandler` will be called when consumer of resulting Observable
- * unsubscribes from it.
- *
- * In some APIs unregistering is actually handled differently. Method registering an event handler
- * returns some kind of token, which is later used to identify which function should
- * be unregistered or it itself has method that unregisters event handler.
- * If that is the case with your API, make sure token returned
- * by registering method is returned by `addHandler`. Then it will be passed
- * as a second argument to `removeHandler`, where you will be able to use it.
- *
- * If you need access to all event handler parameters (not only the first one),
- * or you need to transform them in any way, you can call `fromEventPattern` with optional
- * third parameter - project function which will accept all arguments passed to
- * event handler when it is called. Whatever is returned from project function will appear on
- * resulting stream instead of usual event handlers first argument. This means
- * that default project can be thought of as function that takes its first parameter
- * and ignores the rest.
- *
- * ## Examples
- *
- * Emits clicks happening on the DOM document
- *
- * ```ts
- * import { fromEventPattern } from 'rxjs';
- *
- * function addClickHandler(handler) {
- *   document.addEventListener('click', handler);
- * }
- *
- * function removeClickHandler(handler) {
- *   document.removeEventListener('click', handler);
- * }
- *
- * const clicks = fromEventPattern(
- *   addClickHandler,
- *   removeClickHandler
- * );
- * clicks.subscribe(x => console.log(x));
- *
- * // Whenever you click anywhere in the browser, DOM MouseEvent
- * // object will be logged.
- * ```
- *
- * Use with API that returns cancellation token
- *
- * ```ts
- * import { fromEventPattern } from 'rxjs';
- *
- * const token = someAPI.registerEventHandler(function() {});
- * someAPI.unregisterEventHandler(token); // this APIs cancellation method accepts
- *                                        // not handler itself, but special token.
- *
- * const someAPIObservable = fromEventPattern(
- *   function(handler) { return someAPI.registerEventHandler(handler); }, // Note that we return the token here...
- *   function(handler, token) { someAPI.unregisterEventHandler(token); }  // ...to then use it here.
- * );
- * ```
- *
- * Use with project function
- *
- * ```ts
- * import { fromEventPattern } from 'rxjs';
- *
- * someAPI.registerEventHandler((eventType, eventMessage) => {
- *   console.log(eventType, eventMessage); // Logs 'EVENT_TYPE' 'EVENT_MESSAGE' to console.
- * });
- *
- * const someAPIObservable = fromEventPattern(
- *   handler => someAPI.registerEventHandler(handler),
- *   handler => someAPI.unregisterEventHandler(handler)
- *   (eventType, eventMessage) => eventType + ' --- ' + eventMessage // without that function only 'EVENT_TYPE'
- * );                                                                // would be emitted by the Observable
- *
- * someAPIObservable.subscribe(value => console.log(value));
- *
- * // Logs:
- * // 'EVENT_TYPE --- EVENT_MESSAGE'
- * ```
- *
- * @see {@link fromEvent}
- * @see {@link bindCallback}
- * @see {@link bindNodeCallback}
- *
- * @param addHandler A function that takes a `handler` function as argument and attaches it
- * somehow to the actual source of events.
- * @param removeHandler A function that takes a `handler` function as an argument and removes
- * it from the event source. If `addHandler` returns some kind of token, `removeHandler` function
- * will have it as a second parameter.
- * @param resultSelector A function to transform results. It takes the arguments from the event
- * handler and should return a single value.
- * @return Observable which, when an event happens, emits first parameter passed to registered
- * event handler. Alternatively it emits whatever project function returns at that moment.
- */
-export function fromEventPattern<T>(
-  addHandler: (handler: NodeEventHandler) => any,
-  removeHandler?: (handler: NodeEventHandler, signal?: any) => void,
-  resultSelector?: (...args: any[]) => T
-): Observable<T | T[]> {
-  if (resultSelector) {
-    return fromEventPattern<T>(addHandler, removeHandler).pipe(mapOneOrManyArgs(resultSelector));
-  }
-
-  return new Observable<T | T[]>((subscriber) => {
-    const handler = (...e: T[]) => subscriber.next(e.length === 1 ? e[0] : e);
-    const retValue = addHandler(handler);
-    return isFunction(removeHandler) ? () => removeHandler(handler, retValue) : undefined;
-  });
-}

package/src/node_modules/rxjs/src/internal/observable/fromSubscribable.ts

@@ -1,17 +0,0 @@
-import { Observable } from '../Observable';
-import { Subscriber } from '../Subscriber';
-import { Subscribable } from '../types';
-
-/**
- * Used to convert a subscribable to an observable.
- *
- * Currently, this is only used within internals.
- *
- * TODO: Discuss ObservableInput supporting "Subscribable".
- * https://github.com/ReactiveX/rxjs/issues/5909
- *
- * @param subscribable A subscribable
- */
-export function fromSubscribable<T>(subscribable: Subscribable<T>) {
-  return new Observable((subscriber: Subscriber<T>) => subscribable.subscribe(subscriber));
-}