@khanacademy/wonder-blocks-testing 8.0.20 → 8.0.21

package/dist/response-impl.js.flow

@@ -1,7 +0,0 @@
-/**
- * Flowtype definitions for data
- * Generated by Flowgen from a Typescript Definition
- * Flowgen v1.21.0
- * @flow
- */
-declare export var ResponseImpl: typeof Response;

package/dist/settle-controller.js.flow

@@ -1,25 +0,0 @@
-/**
- * Flowtype definitions for data
- * Generated by Flowgen from a Typescript Definition
- * Flowgen v1.21.0
- * @flow
- */
-import { SettleSignal } from "./settle-signal";
-
-/**
- * A controller for the `RespondWith` API to control response settlement.
- */
-declare export class SettleController {
-  constructor(): this;
-
-  /**
-   * The signal to pass to the `RespondWith` API.
-   */
-  signal: SettleSignal;
-
-  /**
-   * Settle the signal and therefore any associated responses.
-   * @throws {Error} if the signal has already been settled.
-   */
-  settle(): void;
-}

package/dist/settle-signal.js.flow

@@ -1,25 +0,0 @@
-/**
- * Flowtype definitions for data
- * Generated by Flowgen from a Typescript Definition
- * Flowgen v1.21.0
- * @flow
- */
-/**
- * A signal for controlling the `RespondWith` API responses.
- *
- * This provide finely-grained control over the promise lifecycle to support
- * complex test scenarios.
- */
-declare export class SettleSignal extends EventTarget {
-  constructor(setSettleFn?: ((settleFn: () => void) => mixed) | null): this;
-
-  /**
-   * An already settled signal.
-   */
-  static settle(): SettleSignal;
-
-  /**
-   * Has this signal been settled yet?
-   */
-  settled: boolean;
-}

package/dist/types.js.flow

@@ -1,40 +0,0 @@
-/**
- * Flowtype definitions for data
- * Generated by Flowgen from a Typescript Definition
- * Flowgen v1.21.0
- * @flow
- */
-import type { MockResponse } from "./respond-with";
-
-/**
- * A valid GraphQL response as supported by our mocking framework.
- * Note that we don't currently support both data and errors being set.
- */
-export type GraphQLJson<TData: { [key: any]: any }> =
-  | {|
-      data: TData,
-    |}
-  | {|
-      errors: Array<{|
-        message: string,
-      |}>,
-    |};
-export type MockFn<TOperationType> = {|
-  (...args: Array<any>): Promise<Response>,
-  mockOperation: MockOperationFn<TOperationType>,
-  mockOperationOnce: MockOperationFn<TOperationType>,
-|};
-export type OperationMock<TOperation> = {|
-  operation: TOperation,
-  onceOnly: boolean,
-  used: boolean,
-  response: () => Promise<Response>,
-|};
-export type OperationMatcher<TOperation> = (
-  operation: TOperation,
-  ...args: Array<any>
-) => boolean;
-export type MockOperationFn<TOperationType> = <TOperation: TOperationType>(
-  operation: TOperation,
-  response: MockResponse<any>
-) => MockFn<TOperationType>;

package/src/harness/adapters/adapters.js.flow

@@ -1,28 +0,0 @@
-/**
- * @flow
- */
-import * as css from "./css";
-import * as data from "./data";
-import * as portal from "./portal";
-import * as router from "./router";
-
-import type { TestHarnessConfigs, TestHarnessConfig } from "../types";
-
-/**
- * NOTE: We do not type `DefaultAdapters` with `Adapters` here because we want
- * the individual config types of each adapter to remain intact rather than
- * getting changed to `any`.
- */
-/**
- * The default adapters provided by Wonder Blocks.
- */
-declare export var DefaultAdapters: {|
-  +css: typeof css.adapter,
-  +data: typeof data.adapter,
-  +portal: typeof portal.adapter,
-  +router: typeof router.adapter,
-|};
-/**
- * The default configurations to use with the `DefaultAdapters`.
- */
-declare export var DefaultConfigs: TestHarnessConfigs<typeof DefaultAdapters>;

package/src/harness/adapters/router.jsx.flow

@@ -1,112 +0,0 @@
-/**
- * @flow
- */
-import * as React from "react";
-import { MemoryRouter } from "react-router-dom";
-import type { LocationShape } from "react-router-dom";
-import type { TestHarnessAdapter } from "../types";
-declare type MemoryRouterProps = React.ElementConfig<typeof MemoryRouter>;
-
-/**
- * Configuration for the withLocation test harness adapter.
- */
-declare type Config =
-  | $ReadOnly<
-      | {|
-          /**
-           * See MemoryRouter prop for initialEntries.
-           */
-          initialEntries: $PropertyType<MemoryRouterProps, "initialEntries">,
-
-          /**
-           * See MemoryRouter prop for initialIndex.
-           */
-          initialIndex?: $PropertyType<MemoryRouterProps, "initialIndex">,
-
-          /**
-           * See MemoryRouter prop for getUserConfirmation.
-           */
-          getUserConfirmation?: $PropertyType<
-            MemoryRouterProps,
-            "getUserConfirmation"
-          >,
-
-          /**
-           * A path match to use.
-           *
-           * When this is specified, the harnessed component will be
-           * rendered inside a `Route` handler with this path.
-           *
-           * If the path matches the location, then the route will
-           * render the component.
-           *
-           * If the path does not match the location, then the route
-           * will not render the component.
-           */
-          path?: string,
-        |}
-      | {|
-          /**
-           * The location to use.
-           */
-          location: string | LocationShape,
-
-          /**
-           * Force the use of a StaticRouter, instead of MemoryRouter.
-           */
-          forceStatic: true,
-
-          /**
-           * A path match to use.
-           *
-           * When this is specified, the harnessed component will be
-           * rendered inside a `Route` handler with this path.
-           *
-           * If the path matches the location, then the route will
-           * render the component.
-           *
-           * If the path does not match the location, then the route
-           * will not render the component.
-           */
-          path?: string,
-        |}
-      | {|
-          /**
-           * The initial location to use.
-           */
-          location: string | LocationShape,
-
-          /**
-           * A path match to use.
-           *
-           * When this is specified, the harnessed component will be
-           * rendered inside a `Route` handler with this path.
-           *
-           * If the path matches the location, then the route will
-           * render the component.
-           *
-           * If the path does not match the location, then the route
-           * will not render the component.
-           */
-          path?: string,
-        |}
-    >
-  | string;
-/**
- * The default configuration for this adapter.
- */
-declare export var defaultConfig: {|
-  +location: "/",
-|};
-/**
- * Adapter that sets up a router and AppShell location-specific contexts.
- *
- * This allows you to ensure that components are being tested in the
- * AppShell world.
- *
- * NOTE(somewhatabstract): The AppShell component itself already does
- * the work of setting up routing and the AppShellContext and so using this
- * adapter with the App component will have zero-effect since AppShell will
- * override it.
- */
-declare export var adapter: TestHarnessAdapter<Config>;

package/src/harness/make-test-harness.js.flow

@@ -1,22 +0,0 @@
-// @flow
-import * as React from "react";
-import type {TestHarnessAdapters, TestHarnessConfigs} from "./types";
-
-/**
- * Create a test harness method for use with React components.
- *
- * This returns a test harness method that applies the default configurations
- * to the given adapters, wrapping a given component.
- * @param {TAdapters} adapters All the adapters to be supported by the returned
- * test harness.
- * @param {Configs<TAdapters>} defaultConfigs Default configuration values for
- * the adapters.
- * @returns A test harness.
- */
-declare export var makeTestHarness: <TAdapters: TestHarnessAdapters>(
-    adapters: TAdapters,
-    defaultConfigs: TestHarnessConfigs<TAdapters>,
-) => <-TProps, +Instance = mixed>(
-    Component: React.AbstractComponent<TProps, Instance>,
-    configs?: $Shape<TestHarnessConfigs<TAdapters>>,
-) => React.AbstractComponent<TProps, Instance>;

package/src/harness/types.js.flow

@@ -1,57 +0,0 @@
-// @flow
-import * as React from "react";
-
-/**
- * A adapter to be composed with our test harnass infrastructure.
- */
-export type TestHarnessAdapter<TConfig> = (
-    children: React.Node,
-    config: TConfig,
-) => React.Element<any>;
-
-/**
- * A general map of adapters by their identifiers.
- *
- * It's OK that this has `any` for the config type as this is the very base
- * version of a adapter set. In reality, a more specific type will be used
- * with the harness functions that use more specific definitions of known
- * adapters. This is just to support the base reality of not knowing.
- *
- * Use this on input positions only. Output positions for adapters
- * should infer their type in most cases to ensure the strongest typing of
- * the adapters.
- */
-export type TestHarnessAdapters = {|
-    +[adapterID: string]: TestHarnessAdapter<any>,
-|};
-
-/**
- * Mapping functions from a adapter-like function to config type.
- */
-type ExtractConfig = <TConfig>(TestHarnessAdapter<TConfig>) => TConfig;
-type ExtractMaybeConfig = <TConfig>(TestHarnessAdapter<TConfig>) => ?TConfig;
-
-/**
- * Type for easily defining an adapter's config type.
- *
- * This is the `TestHarnessAdapter` equivalent of `React.ElementConfig`.
- */
-export type TestHarnessConfig<TAdapter> = $Call<ExtractConfig, TAdapter>;
-
-/**
- * The `TestHarnessConfigs` type as defined by parsing a given set of adapters.
- *
- * NOTE: This only works if the properties of the passed `TAdapters` type
- * are explicitly typed as `TestHarnessAdapter<TConfig>` so if passing in a
- * non-Adapters type (which we should be, to get strong `TConfig` types instead
- * of `any`), then that object should make sure that each adapter is strongly
- * marked as `TestHarnessAdapter<TConfig>` - flow does not appear to pattern
- * match against the type definition when invoking the `ExtractConfig` type and I
- * haven't worked out how to get it to multi-dispatch so that it matches
- * functions too. Even worse, if the type doesn't match, it just allows `any`
- * in the `Configs` object, rather than indicating any kind of problem.
- */
-export type TestHarnessConfigs<TAdapters: TestHarnessAdapters> = $ObjMap<
-    TAdapters,
-    ExtractMaybeConfig,
->;