@khanacademy/wonder-blocks-data 10.1.0 → 10.1.1

package/src/hooks/{use-cached-effect.js → use-cached-effect.ts}

@@ -1,4 +1,3 @@
-// @flow
 import * as React from "react";
 import {useForceUpdate} from "@khanacademy/wonder-blocks-core";
 import {DataError, DataErrors} from "../util/data-error";
@@ -13,15 +12,14 @@ import type {Result, ValidCacheData} from "../util/types";
 
 import {FetchPolicy} from "../util/types";
 
-type CachedEffectOptions<TData: ValidCacheData> = {|
+type CachedEffectOptions<TData extends ValidCacheData> = {
     /**
      * The policy to use when determining how to retrieve the request data from
      * cache and network.
      *
      * Defaults to `FetchPolicy.CacheBeforeNetwork`.
      */
-    fetchPolicy?: $Values<typeof FetchPolicy>,
-
+    fetchPolicy?: typeof FetchPolicy[keyof typeof FetchPolicy];
     /**
      * When `true`, the effect will not be executed; otherwise, the effect will
      * be executed.
@@ -31,8 +29,7 @@ type CachedEffectOptions<TData: ValidCacheData> = {|
      *
      * Default is `false`.
      */
-    skip?: boolean,
-
+    skip?: boolean;
     /**
      * When `true`, the effect will not reset the result to the loading status
      * while executing if the requestId changes, instead, returning
@@ -43,8 +40,7 @@ type CachedEffectOptions<TData: ValidCacheData> = {|
      * loading; old pending effects are discarded on changes and as such this
      * value has no effect in that case.
      */
-    retainResultOnChange?: boolean,
-
+    retainResultOnChange?: boolean;
     /**
      * Callback that is invoked if the result for the given hook has changed.
      *
@@ -55,8 +51,7 @@ type CachedEffectOptions<TData: ValidCacheData> = {|
      * When not defined, the hook will ensure the component re-renders to pick
      * up the latest result.
      */
-    onResultChanged?: (result: Result<TData>) => void,
-
+    onResultChanged?: (result: Result<TData>) => void;
     /**
      * Scope to use with the shared cache.
      *
@@ -65,8 +60,8 @@ type CachedEffectOptions<TData: ValidCacheData> = {|
      *
      * Changing this value after the first call is not supported.
      */
-    scope?: string,
-|};
+    scope?: string;
+};
 
 const DefaultScope = "useCachedEffect";
 
@@ -86,12 +81,12 @@ const DefaultScope = "useCachedEffect";
  * Once the request has been tried once and a non-loading response has been
  * cached, the request will not executed made again.
  */
-export const useCachedEffect = <TData: ValidCacheData>(
+export const useCachedEffect = <TData extends ValidCacheData>(
     requestId: string,
     handler: () => Promise<TData>,
-    options: CachedEffectOptions<TData> = ({}: $Shape<
-        CachedEffectOptions<TData>,
-    >),
+    options: CachedEffectOptions<TData> = {} as Partial<
+        CachedEffectOptions<TData>
+    >,
 ): [Result<TData>, () => void] => {
     const {
         fetchPolicy = FetchPolicy.CacheBeforeNetwork,
@@ -108,13 +103,13 @@ export const useCachedEffect = <TData: ValidCacheData>(
     // Instead of using state, which would be local to just this hook instance,
     // we use a shared in-memory cache.
     const [mostRecentResult, setMostRecentResult] = useSharedCache<
-        Result<TData>,
-    >(
-        requestId, // The key of the cached item
-        scope, // The scope of the cached items
+        Result<TData>
+    >( // The key of the cached item
+        requestId, // The scope of the cached items
         // No default value. We don't want the loading status there; to ensure
         // that all calls when the request is in-flight will update once that
         // request is done, we want the cache to be empty until that point.
+        scope,
     );
     const forceUpdate = useForceUpdate();
     // For the NetworkOnly fetch policy, we ignore the cached value.
@@ -127,8 +122,11 @@ export const useCachedEffect = <TData: ValidCacheData>(
         // We aren't using useCallback here because we need to make sure that
         // if we are rememo-izing, we cancel any inflight request for the old
         // callback.
+        // @ts-expect-error [FEI-5019] - TS2339 - Property 'cancel' does not exist on type 'never'.
         currentRequestRef.current?.cancel();
+        // @ts-expect-error [FEI-5019] - TS2322 - Type 'null' is not assignable to type 'undefined'.
         currentRequestRef.current = null;
+        // @ts-expect-error [FEI-5019] - TS2322 - Type 'null' is not assignable to type 'undefined'.
         networkResultRef.current = null;
 
         const fetchFn = () => {
@@ -155,6 +153,7 @@ export const useCachedEffect = <TData: ValidCacheData>(
                 },
             );
 
+            // @ts-expect-error [FEI-5019] - TS2339 - Property 'request' does not exist on type 'never'.
             if (request === currentRequestRef.current?.request) {
                 // The request inflight is the same, so do nothing.
                 // NOTE: Perhaps if invoked via a refetch, we will want to
@@ -163,9 +162,11 @@ export const useCachedEffect = <TData: ValidCacheData>(
             }
 
             // Clear the last network result.
+            // @ts-expect-error [FEI-5019] - TS2322 - Type 'null' is not assignable to type 'undefined'.
             networkResultRef.current = null;
 
             // Cancel the previous request.
+            // @ts-expect-error [FEI-5019] - TS2339 - Property 'cancel' does not exist on type 'never'.
             currentRequestRef.current?.cancel();
 
             // TODO(somewhatabstract, FEI-4276):
@@ -177,6 +178,7 @@ export const useCachedEffect = <TData: ValidCacheData>(
             // Catching shouldn't serve a purpose.
             // eslint-disable-next-line promise/catch-or-return
             request.then((result) => {
+                // @ts-expect-error [FEI-5019] - TS2322 - Type 'null' is not assignable to type 'undefined'.
                 currentRequestRef.current = null;
                 if (cancel) {
                     // We don't modify our result if the request was cancelled
@@ -187,6 +189,7 @@ export const useCachedEffect = <TData: ValidCacheData>(
 
                 // Now we need to update the cache and notify or force a rerender.
                 setMostRecentResult(result);
+                // @ts-expect-error [FEI-5019] - TS2322 - Type 'Result<TData>' is not assignable to type 'undefined'.
                 networkResultRef.current = result;
 
                 if (onResultChanged != null) {
@@ -201,6 +204,7 @@ export const useCachedEffect = <TData: ValidCacheData>(
                 return; // Shut up eslint always-return rule.
             });
 
+            // @ts-expect-error [FEI-5019] - TS2322 - Type '{ requestId: string; request: Promise<Result<TData>>; cancel(): void; }' is not assignable to type 'undefined'.
             currentRequestRef.current = {
                 requestId,
                 request,
@@ -261,7 +265,9 @@ export const useCachedEffect = <TData: ValidCacheData>(
         }
         fetchRequest();
         return () => {
+            // @ts-expect-error [FEI-5019] - TS2339 - Property 'cancel' does not exist on type 'never'.
             currentRequestRef.current?.cancel();
+            // @ts-expect-error [FEI-5019] - TS2322 - Type 'null' is not assignable to type 'undefined'.
             currentRequestRef.current = null;
         };
     }, [shouldFetch, fetchRequest]);
@@ -282,5 +288,6 @@ export const useCachedEffect = <TData: ValidCacheData>(
     lastResultAgnosticOfIdRef.current = result;
 
     // We return the result and a function for triggering a refetch.
+    // @ts-expect-error [FEI-5019] - TS2322 - Type '{ status: "loading"; } | { status: "error"; error: Error; } | { status: "aborted"; } | { status: "success"; data: ValidCacheData; }' is not assignable to type 'Result<TData>'.
     return [result, fetchRequest];
 };

package/src/hooks/{use-gql-router-context.js → use-gql-router-context.ts}

@@ -1,4 +1,3 @@
-// @flow
 import {useContext, useRef, useMemo} from "react";
 
 import {mergeGqlContext} from "../util/merge-gql-context";
@@ -10,8 +9,8 @@ import type {GqlRouterConfiguration, GqlContext} from "../util/gql-types";
 /**
  * Construct a GqlRouterContext from the current one and partial context.
  */
-export const useGqlRouterContext = <TContext: GqlContext>(
-    contextOverrides: Partial<TContext> = ({}: $Shape<TContext>),
+export const useGqlRouterContext = <TContext extends GqlContext>(
+    contextOverrides: Partial<TContext> = {} as Partial<TContext>,
 ): GqlRouterConfiguration<TContext> => {
     // This hook only works if the `GqlRouter` has been used to setup context.
     const gqlRouterContext = useContext(GqlRouterContext);

package/src/hooks/{use-gql.js → use-gql.ts}

@@ -1,4 +1,3 @@
-// @flow
 import {useCallback} from "react";
 
 import {mergeGqlContext} from "../util/merge-gql-context";
@@ -21,9 +20,9 @@ import type {
  * Values in the partial context given to the returned fetch function will
  * only be included if they have a value other than undefined.
  */
-export const useGql = <TContext: GqlContext>(
-    context: Partial<TContext> = ({}: $Shape<TContext>),
-): (<TData, TVariables: {...}>(
+export const useGql = <TContext extends GqlContext>(
+    context: Partial<TContext> = {} as Partial<TContext>,
+): (<TData, TVariables extends Record<any, any>>(
     operation: GqlOperation<TData, TVariables>,
     options?: GqlFetchOptions<TVariables, TContext>,
 ) => Promise<TData>) => {
@@ -36,7 +35,7 @@ export const useGql = <TContext: GqlContext>(
     // making a new one. That then means they can safely use the return value
     // in hooks deps without fear of it triggering extra renders.
     const gqlFetch = useCallback(
-        <TData, TVariables: {...}>(
+        <TData, TVariables extends Record<any, any>>(
             operation: GqlOperation<TData, TVariables>,
             options: GqlFetchOptions<TVariables, TContext> = Object.freeze({}),
         ) => {
@@ -51,5 +50,6 @@ export const useGql = <TContext: GqlContext>(
         },
         [gqlRouterContext],
     );
+    // @ts-expect-error [FEI-5019] - TS2322 - Type '<TData, TVariables extends Record<any, any>>(operation: GqlOperation<TData, TVariables>, options?: GqlFetchOptions<TVariables, TContext>) => Promise<unknown>' is not assignable to type '<TData, TVariables extends Record<any, any>>(operation: GqlOperation<TData, TVariables>, options?: GqlFetchOptions<TVariables, TContext> | undefined) => Promise<...>'.
     return gqlFetch;
 };

package/src/hooks/{use-hydratable-effect.js → use-hydratable-effect.ts}

@@ -1,4 +1,3 @@
-// @flow
 import * as React from "react";
 
 import {useServerEffect} from "./use-server-effect";
@@ -21,7 +20,7 @@ export const WhenClientSide = {
      * for properly hydrating this component (for example, the action invokes
      * Apollo which manages its own cache to ensure things render properly).
      */
-    DoNotHydrate: ("DoNotHydrate": "DoNotHydrate"),
+    DoNotHydrate: "DoNotHydrate" as const,
 
     /**
      * The result from executing the effect server-side will be hydrated.
@@ -29,7 +28,7 @@ export const WhenClientSide = {
      * be hydrated (i.e. both error and success hydration results prevent the
      * effect running client-side).
      */
-    ExecuteWhenNoResult: ("ExecuteWhenNoResult": "ExecuteWhenNoResult"),
+    ExecuteWhenNoResult: "ExecuteWhenNoResult" as const,
 
     /**
      * The result from executing the effect server-side will be hydrated.
@@ -38,18 +37,17 @@ export const WhenClientSide = {
      * If the hydrated result was not a success result, or there was no
      * hydrated result, the effect will not be executed.
      */
-    ExecuteWhenNoSuccessResult:
-        ("ExecuteWhenNoSuccessResult": "ExecuteWhenNoSuccessResult"),
+    ExecuteWhenNoSuccessResult: "ExecuteWhenNoSuccessResult" as const,
 
     /**
      * The result from executing the effect server-side will be hydrated.
      * The effect will always be executed client-side, regardless of the
      * hydrated result status.
      */
-    AlwaysExecute: ("AlwaysExecute": "AlwaysExecute"),
-};
+    AlwaysExecute: "AlwaysExecute" as const,
+} as const;
 
-type HydratableEffectOptions<TData: ValidCacheData> = {|
+type HydratableEffectOptions<TData extends ValidCacheData> = {
     /**
      * How the hook should behave when rendering client-side for the first time.
      *
@@ -60,8 +58,7 @@ type HydratableEffectOptions<TData: ValidCacheData> = {|
      * Changing this value after the first call is irrelevant as it only
      * affects the initial render behavior.
      */
-    clientBehavior?: $Values<typeof WhenClientSide>,
-
+    clientBehavior?: typeof WhenClientSide[keyof typeof WhenClientSide];
     /**
      * When `true`, the effect will not be executed; otherwise, the effect will
      * be executed.
@@ -71,8 +68,7 @@ type HydratableEffectOptions<TData: ValidCacheData> = {|
      *
      * Default is `false`.
      */
-    skip?: boolean,
-
+    skip?: boolean;
     /**
      * When `true`, the effect will not reset the result to the loading status
      * while executing if the requestId changes, instead, returning
@@ -83,8 +79,7 @@ type HydratableEffectOptions<TData: ValidCacheData> = {|
      * loading; old pending effects are discarded on changes and as such this
      * value has no effect in that case.
      */
-    retainResultOnChange?: boolean,
-
+    retainResultOnChange?: boolean;
     /**
      * Callback that is invoked if the result for the given hook has changed.
      *
@@ -95,8 +90,7 @@ type HydratableEffectOptions<TData: ValidCacheData> = {|
      * When not defined, the hook will ensure the component re-renders to pick
      * up the latest result.
      */
-    onResultChanged?: (result: Result<TData>) => void,
-
+    onResultChanged?: (result: Result<TData>) => void;
     /**
      * Scope to use with the shared cache.
      *
@@ -105,8 +99,8 @@ type HydratableEffectOptions<TData: ValidCacheData> = {|
      *
      * Changing this value after the first call is not supported.
      */
-    scope?: string,
-|};
+    scope?: string;
+};
 
 const DefaultScope = "useHydratableEffect";
 
@@ -120,12 +114,12 @@ const DefaultScope = "useHydratableEffect";
  * invocations. Cache changes from one hook instance do not trigger renders
  * in components that use the same requestID.
  */
-export const useHydratableEffect = <TData: ValidCacheData>(
+export const useHydratableEffect = <TData extends ValidCacheData>(
     requestId: string,
     handler: () => Promise<TData>,
-    options: HydratableEffectOptions<TData> = ({}: $Shape<
-        HydratableEffectOptions<TData>,
-    >),
+    options: HydratableEffectOptions<TData> = {} as Partial<
+        HydratableEffectOptions<TData>
+    >,
 ): Result<TData> => {
     const {
         clientBehavior = WhenClientSide.ExecuteWhenNoSuccessResult,
@@ -144,48 +138,49 @@ export const useHydratableEffect = <TData: ValidCacheData>(
         skip,
     });
 
-    const getDefaultCacheValue: () => ?Result<TData> = React.useCallback(() => {
-        // If we don't have a requestId, it's our first render, the one
-        // where we hydrated. So defer to our clientBehavior value.
-        switch (clientBehavior) {
-            case WhenClientSide.DoNotHydrate:
-            case WhenClientSide.AlwaysExecute:
-                // Either we weren't hydrating at all, or we don't care
-                // if we hydrated something or not, either way, we're
-                // doing a request.
-                return null;
-
-            case WhenClientSide.ExecuteWhenNoResult:
-                // We only execute if we didn't hydrate something.
-                // So, returning the hydration result as default for our
-                // cache, will then prevent the cached effect running.
-                return serverResult;
-
-            case WhenClientSide.ExecuteWhenNoSuccessResult:
-                // We only execute if we didn't hydrate a success result.
-                if (serverResult?.status === "success") {
+    const getDefaultCacheValue: () => Result<TData> | null | undefined =
+        React.useCallback(() => {
+            // If we don't have a requestId, it's our first render, the one
+            // where we hydrated. So defer to our clientBehavior value.
+            switch (clientBehavior) {
+                case WhenClientSide.DoNotHydrate:
+                case WhenClientSide.AlwaysExecute:
+                    // Either we weren't hydrating at all, or we don't care
+                    // if we hydrated something or not, either way, we're
+                    // doing a request.
+                    return null;
+
+                case WhenClientSide.ExecuteWhenNoResult:
+                    // We only execute if we didn't hydrate something.
                     // So, returning the hydration result as default for our
                     // cache, will then prevent the cached effect running.
                     return serverResult;
-                }
-                return null;
-        }
-        // There is no reason for this to change after the first render,
-        // you might think, but the function closes around serverResult and if
-        // the requestId changes, it still returns the hydrate result of the
-        // first render of the previous requestId. This then means that the
-        // hydrate result is still the same, and the effect is not re-executed
-        // because the cache gets incorrectly defaulted.
-        // However, we don't want to bother doing anything with this on
-        // client behavior changing since that truly is irrelevant.
-        // eslint-disable-next-line react-hooks/exhaustive-deps
-    }, [serverResult]);
+
+                case WhenClientSide.ExecuteWhenNoSuccessResult:
+                    // We only execute if we didn't hydrate a success result.
+                    if (serverResult?.status === "success") {
+                        // So, returning the hydration result as default for our
+                        // cache, will then prevent the cached effect running.
+                        return serverResult;
+                    }
+                    return null;
+            }
+            // There is no reason for this to change after the first render,
+            // you might think, but the function closes around serverResult and if
+            // the requestId changes, it still returns the hydrate result of the
+            // first render of the previous requestId. This then means that the
+            // hydrate result is still the same, and the effect is not re-executed
+            // because the cache gets incorrectly defaulted.
+            // However, we don't want to bother doing anything with this on
+            // client behavior changing since that truly is irrelevant.
+            // eslint-disable-next-line react-hooks/exhaustive-deps
+        }, [serverResult]);
 
     // Instead of using state, which would be local to just this hook instance,
     // we use a shared in-memory cache.
-    useSharedCache<Result<TData>>(
-        requestId, // The key of the cached item
-        scope, // The scope of the cached items
+    useSharedCache<Result<TData>>( // The key of the cached item
+        requestId, // The scope of the cached items
+        scope,
         getDefaultCacheValue,
     );
 

package/src/hooks/{use-request-interception.js → use-request-interception.ts}

@@ -1,4 +1,3 @@
-// @flow
 import * as React from "react";
 
 import InterceptContext from "../components/intercept-context";
@@ -16,7 +15,7 @@ import type {ValidCacheData} from "../util/types";
  * an intercepted handler, and then invoke `useServerEffect` (or other things)
  * with that intercepted handler.
  */
-export const useRequestInterception = <TData: ValidCacheData>(
+export const useRequestInterception = <TData extends ValidCacheData>(
     requestId: string,
     handler: () => Promise<TData>,
 ): (() => Promise<TData>) => {
@@ -32,6 +31,7 @@ export const useRequestInterception = <TData: ValidCacheData>(
         // Call the interceptors from closest to furthest.
         // If one returns a non-null result, then we keep that.
         const interceptResponse = interceptors.reduceRight(
+            // @ts-expect-error [FEI-5019] - TS2769 - No overload matches this call.
             (prev, interceptor) => {
                 if (prev != null) {
                     return prev;
@@ -42,8 +42,8 @@ export const useRequestInterception = <TData: ValidCacheData>(
         );
         // If nothing intercepted this request, invoke the original handler.
         // NOTE: We can't guarantee all interceptors return the same type
-        // as our handler, so how can flow know? Let's just suppress that.
-        // $FlowFixMe[incompatible-return]
+        // as our handler, so how can TypeScript know? Let's just suppress that.
+        // @ts-expect-error [FEI-5019] - TS2739 - Type '(requestId: string) => Promise<ValidCacheData | null | undefined> | null | undefined' is missing the following properties from type 'Promise<TData>': then, catch, finally, [Symbol.toStringTag]
         return interceptResponse ?? handler();
     }, [handler, interceptors, requestId]);
 

package/src/hooks/{use-server-effect.js → use-server-effect.ts}

@@ -1,4 +1,3 @@
-// @flow
 import {Server} from "@khanacademy/wonder-blocks-core";
 import {useContext} from "react";
 import {TrackerContext} from "../util/request-tracking";
@@ -8,7 +7,7 @@ import {useRequestInterception} from "./use-request-interception";
 
 import type {Result, ValidCacheData} from "../util/types";
 
-type ServerEffectOptions = {|
+type ServerEffectOptions = {
     /**
      * When `true`, the result of the effect when fulfilled using Wonder Blocks
      * Data will be stored in the hydration cache for hydrating client-side;
@@ -20,16 +19,15 @@ type ServerEffectOptions = {|
      *
      * Default is `true`.
      */
-    hydrate?: boolean,
-
+    hydrate?: boolean;
     /**
      * When `true`, the effect will not be tracked for fulfillment; otherwise,
      * the effect will be tracked for fulfillment.
      *
      * Default is `false`.
      */
-    skip?: boolean,
-|};
+    skip?: boolean;
+};
 
 /**
  * Hook to perform an asynchronous action during server-side rendering.
@@ -46,11 +44,11 @@ type ServerEffectOptions = {|
  *
  * The asynchronous action is never invoked on the client-side.
  */
-export const useServerEffect = <TData: ValidCacheData>(
+export const useServerEffect = <TData extends ValidCacheData>(
     requestId: string,
     handler: () => Promise<TData>,
-    options: ServerEffectOptions = ({}: $Shape<ServerEffectOptions>),
-): ?Result<TData> => {
+    options: ServerEffectOptions = {} as Partial<ServerEffectOptions>,
+): Result<TData> | null | undefined => {
     const {hydrate = true, skip = false} = options;
 
     // Plug in to the request interception framework for code that wants

package/src/hooks/{use-shared-cache.js → use-shared-cache.ts}

@@ -1,4 +1,3 @@
-// @flow
 import * as React from "react";
 import {DataError, DataErrors} from "../util/data-error";
 import {ScopedInMemoryCache} from "../util/scoped-in-memory-cache";
@@ -7,7 +6,9 @@ import type {ValidCacheData, ScopedCache} from "../util/types";
 /**
  * A function for inserting a value into the cache or clearing it.
  */
-type CacheValueFn<TValue: ValidCacheData> = (value: ?TValue) => void;
+type CacheValueFn<TValue extends ValidCacheData> = (
+    value?: TValue | null | undefined,
+) => void;
 
 /**
  * This is the cache.
@@ -42,11 +43,15 @@ export const SharedCache: ScopedCache = cache;
  * sure this toggling is optional - or we could use a callback argument, to
  * achieve this on an as-needed basis.
  */
-export const useSharedCache = <TValue: ValidCacheData>(
+export const useSharedCache = <TValue extends ValidCacheData>(
     id: string,
     scope: string,
-    initialValue?: ?TValue | (() => ?TValue),
-): [?TValue, CacheValueFn<TValue>] => {
+    initialValue?:
+        | TValue
+        | null
+        | undefined
+        | (() => TValue | null | undefined),
+): [TValue | null | undefined, CacheValueFn<TValue>] => {
     // Verify arguments.
     if (!id || typeof id !== "string") {
         throw new DataError(
@@ -65,7 +70,7 @@ export const useSharedCache = <TValue: ValidCacheData>(
     // Memoize our APIs.
     // This one allows callers to set or replace the cached value.
     const cacheValue = React.useCallback(
-        (value: ?TValue) =>
+        (value?: TValue | null) =>
             value == null
                 ? cache.purge(scope, id)
                 : cache.set(scope, id, value),
@@ -76,8 +81,8 @@ export const useSharedCache = <TValue: ValidCacheData>(
     // since our last run through. Also, our cache does not know what type it
     // stores, so we have to cast it to the type we're exporting. This is a
     // dev time courtesy, rather than a runtime thing.
-    // $FlowIgnore[incompatible-type]
-    let currentValue: ?TValue = cache.get(scope, id);
+    // @ts-expect-error [FEI-5019] - TS2322 - Type 'ValidCacheData | null | undefined' is not assignable to type 'TValue | null | undefined'.
+    let currentValue: TValue | null | undefined = cache.get(scope, id);
 
     // If we have an initial value, we need to add it to the cache
     // and use it as our current value.

package/src/{index.js → index.ts}

@@ -1,4 +1,3 @@
-// @flow
 export {FetchPolicy} from "./util/types";
 export type {
     ErrorOptions,

package/src/util/__tests__/{get-gql-data-from-response.test.js → get-gql-data-from-response.test.ts}

@@ -1,4 +1,3 @@
-// @flow
 import {getGqlDataFromResponse} from "../get-gql-data-from-response";
 
 describe("#getGqlDataFromReponse", () => {

package/src/util/__tests__/{get-gql-request-id.test.js → get-gql-request-id.test.ts}

@@ -1,5 +1,3 @@
-// @flow
-
 import {getGqlRequestId} from "../get-gql-request-id";
 
 describe("#getGqlRequestId", () => {
@@ -8,7 +6,7 @@ describe("#getGqlRequestId", () => {
         const operation = {
             type: "query",
             id: "myQuery",
-        };
+        } as const;
 
         // Act
         const requestId = getGqlRequestId(operation, null, {
@@ -27,12 +25,12 @@ describe("#getGqlRequestId", () => {
         const operation = {
             type: "query",
             id: "myQuery",
-        };
+        } as const;
         const context = {
             context3: "value3",
             context2: "value2",
             context1: "value1",
-        };
+        } as const;
 
         // Act
         const requestId = getGqlRequestId(operation, null, context);
@@ -49,14 +47,14 @@ describe("#getGqlRequestId", () => {
         const operation = {
             type: "query",
             id: "myQuery",
-        };
+        } as const;
         const variables = {
             variable4: null,
             variable2: 42,
             variable1: "value1",
             variable5: true,
             variable3: undefined,
-        };
+        } as const;
 
         // Act
         const requestId = getGqlRequestId(operation, variables, {
@@ -77,7 +75,7 @@ describe("#getGqlRequestId", () => {
         const operation = {
             type: "query",
             id: "myQuery",
-        };
+        } as const;
         const variables = {
             variable4: null,
             variable2: 42,
@@ -89,7 +87,7 @@ describe("#getGqlRequestId", () => {
                 nested1: "nested1",
             },
             variable7: [1, 2, 3],
-        };
+        } as const;
 
         // Act
         const requestId = getGqlRequestId(operation, variables, {
@@ -110,13 +108,13 @@ describe("#getGqlRequestId", () => {
         const operation = {
             type: "query",
             id: "myQuery",
-        };
+        } as const;
         const variables = {
             variable1: {
                 date: new Date("2020-01-01"),
                 error: new Error("BOOM!"),
             },
-        };
+        } as const;
 
         // Act
         const requestId = getGqlRequestId(operation, variables, {