Remove flow-type parameters from Relay API references

Summary: Our APIs no longer require explicit flow type annotations. This diff updates the documentation to reflect that.

Reviewed By: voideanvalue

Differential Revision: D48647669

fbshipit-source-id: d141fa5e4dbb24eaff8124351e30c3bd50f22fd7

website/docs/api-reference/hooks/load-query.md

@@ -64,11 +64,6 @@ const queryReference = loadQuery(
 * `environmentProviderOptions`: *[Optional]* options object
     * Options passed to an `environmentProvider` used in `prepareSurfaceEntryPoint.js`.
 
-### Flow Type Parameters
-
-* `TQuery`: Type parameter that should correspond to the Flow type for the specified query. This type is available to import from the the auto-generated file: `<query_name>.graphql.js`.
-* `TEnvironmentProviderOptions`: The type of the `environmentProviderOptions` parameter.
-
 ### Return Value
 
 A query reference with the following properties:

website/docs/api-reference/hooks/use-lazy-load-query.md

@@ -50,10 +50,6 @@ function App() {
     * `fetchKey`: A `fetchKey` can be passed to force a re-evaluation of the current query and variables when the component re-renders, even if the variables didn't change, or even if the component isn't remounted (similarly to how passing a different `key` to a React component will cause it to remount). If the `fetchKey` is different from the one used in the previous render, the current query will be re-evaluated against the store, and it might be refetched depending on the current `fetchPolicy` and the state of the cache.
     * `networkCacheConfig`: *_[Optional] _* Default value: `{force: true}`. Object containing cache config options for the *network layer*. Note that the network layer may contain an *additional* query response cache which will reuse network responses for identical queries. If you want to bypass this cache completely (which is the default behavior), pass `{force: true}` as the value for this option.
 
-### Flow Type Parameters
-
-* `TQuery`: Type parameter that should correspond to the Flow type for the specified query. This type is available to import from the the auto-generated file: `<query_name>.graphql.js`.
-
 ### Return Value
 
 * `data`: Object that contains data which has been read out from the Relay store; the object matches the shape of specified query.

website/docs/api-reference/hooks/use-mutation.md

@@ -70,11 +70,6 @@ function LikeButton() {
 
 <FbUseMutationParameter />
 
-
-### Flow Type Parameters
-
-* `TMutation`: Type parameter that should corresponds the Flow type for the mutation query. This type is available to import from the the auto-generated file: `<mutationName>.graphql.js`.
-
 ### Return Value
 
 Tuple containing the following values:

website/docs/api-reference/hooks/use-subscription.md

@@ -44,13 +44,8 @@ function UserComponent({ id }) {
 * `config`: a config of type [`GraphQLSubscriptionConfig`](#type-graphqlsubscriptionconfigtsubscriptionpayload) passed to [`requestSubscription`](../request-subscription/)
 * `requestSubscriptionFn`: `?<TSubscriptionPayload>(IEnvironment, GraphQLSubscriptionConfig<TSubscriptionPayload>) => Disposable`. An optional function with the same signature as [`requestSubscription`](../request-subscription/), which will be called in its stead. Defaults to `requestSubscription`.
 
-
 <GraphQLSubscriptionConfig />
 
-### Flow Type Parameters
-
-* `TSubscriptionPayload`: The type of the payloads vended by the subscription. You should pass the flow type imported from the auto-generated `.graphql` file corresponding to the subscription, e.g. use `UserDataSubscription` as the type parameter, from `import type {UserDataSubscription} from './__generated__/UserDataSubscription.graphql'`;
-
 ### Behavior
 
 * This is only a thin wrapper around the `requestSubscription` API. It will:

website/docs/api-reference/relay-runtime/commit-mutation.md

@@ -53,14 +53,6 @@ function likeFeedback(environment: IEnvironment): Disposable {
 
 <MutationConfig />
 
-### Flow Type Parameters
-
-* `TMutation`: Type parameter that should corresponds the Flow type for the mutation query. This type is available to import from the the auto-generated file: `<mutationName>.graphql.js`.
-  * Note that this auto-generated type will implement `MutationParameters`.
-
-:::caution
-If you do not **explicitly** pass this type parameter, the variables, optimistic response and response passed to `onCompleted` **will not be type-checked**!
-:::
 
 ### Return Value
 

website/docs/api-reference/relay-runtime/request-subscription.md

@@ -41,10 +41,6 @@ function createSubscription(environment: IEnvironment): Disposable {
 
 <GraphQLSubscriptionConfig />
 
-### Flow Type Parameters
-
-* `TSubscriptionPayload`: The type of the payloads vended by the subscription. You should pass the flow type imported from the auto-generated `.graphql` file corresponding to the subscription, e.g. use `UserDataSubscription` as the type parameter, from `import type {UserDataSubscription} from './__generated__/UserDataSubscription.graphql'`;
-
 ### Return Type
 
 * A [`Disposable`](#interface-disposable) that clears the subscription.