Your React application must be wrapped in the Provider component from this library for the hooks to function properly. No other wrappers (like urql's) are necessary.
Gadget provisions applications with the required <Provider /> component already in place! If using the frontend hosting built into
Gadget, no action is required as this step is already done.
Example:
React
1// import the API client for your specific application from your client package, be sure to replace this package name with your own
The @gadgetinc/react package is intended for use on the client-side only. The hooks provided by this package make requests from your app's frontend directly to your Gadget app's backend from the browser. If you want to use server-side rendering, you can use your framework's server-side data loader support and make imperative calls with your API client object.
manager: The model manager for the model you want to find a record of. Required. Example: api.widget, or api.shopifyProduct
id: The backend id of the record you want to find. Required.
options: Options for making the call to the backend. Not required, and all keys are optional.
select: A list of fields and subfields to select. See select option
requestPolicy: The urql request policy to make the request with. See urql's docs
pause: Set to true to disable this hook. See urql's docs
suspense: Should this hook suspend when fetching data. See suspense
Returns
useFindOne returns two values: a result object with the data, fetching, and error keys for inspecting in your React component's output, and a refetch function to trigger a refresh of the hook's data.
data: GadgetRecord | null: The record fetched from the backend. Is null while the data is being loaded, or if the record wasn't found.
fetching: boolean: A boolean describing if the hook is currently requesting data from the backend.
error: Error | null: An error from the client or server side, if encountered during the request. Will contain an error if the record isn't found by id. See the errors section.
useFindOne expects a record with the given id to be found in the backend database, and will return an error in the error property if no record with this id is found.
useFindOne can select only some fields from the backend model with the select option:
useMaybeFindOne will return data: null and error: null if no record with the given id is found in the backend database. useMaybeFindOne otherwise behaves identically to useFindOne, and accepts the same options.
manager: The model manager for the model you want to find a page of records for. Required. Example: api.widget, or api.shopifyProduct
options: Options for making the call to the backend. Not required and all keys are optional.
select: A list of fields and subfields to select. See the select option docs.
filter: A list of filters to limit the set of returned records. Optional. See the Model Filtering section in your application's API documentation to see the available filters for your models.
search: A search string to match backend records against. Optional. See the Model Searching section in your application's API documentation to see the available search syntax.
sort: A sort order to return backend records by. Optional. See the sorting section in your application's API documentation for more info.
first & after: Pagination arguments to pass to fetch a subsequent page of records from the backend. first should hold a record count and after should hold a string cursor retrieved from the pageInfo of the previous page of results. See the pagination section in your application's API documentation for more info.
last & before: Pagination arguments to pass to fetch a subsequent page of records from the backend. last should hold a record count and before should hold a string cursor retrieved from the pageInfo of the previous page of results. See the pagination section in your application's API documentation for more info.
live: Should this hook re-render when data changes on the backend. See the live option docs.
requestPolicy: The urql request policy to make the request with. See urql's docs
pause: Should the hook make a request right now or not. See urql's docs
suspense: Should this hook suspend when fetching data. See suspense for more info
Returns
useFindMany returns two values: a result object with the data, fetching, and error keys for use in your React component's output, and a refetch function to trigger a refresh of the hook's data.
data: GadgetRecordList | null: The resulting page of records fetched from the backend for your model, once they've arrived
fetching: boolean: A boolean describing if the hook is currently making a request to the backend.
error: Error | null: An error from the client or server side, if encountered during the request. See the errors section.
Without any options, useFindMany will fetch the first page of backend records sorted by id.
useFindMany accepts the select option to allow customization of which fields are returned:
useFindMany accepts a filter option to limit which records are returned from the backend. For example, we can filter to return only widgets created since the start of 2022:
See your app's API reference for more information on which filters are available on what models.
useFindMany accepts a sort option to change the order of the records that are returned. For example, we can sort returned widgets by the createdAt field:
React
1// return the most recently created widgets first
useFindMany accepts a search option to limit the fetched records to only those matching a given search query. For example, we can search all the backend widgets for those matching the string "penny" in any searchable field:
React
// return widgets with "penny" in any searchable field
See your app's API reference for more information on the search query syntax and which fields are searchable.
useFindMany accepts a live option to subscribe to changes in the backend data returned, which will trigger re-renders of your react components as that data changes. For example, we can show an up-to-date view of the first page of backend widgets:
React
// will update when new widgets are created or on-screen widgets are updated
useFindMany accepts pagination arguments for getting the second, third, etc page of results from the backend beyond just the first page. Gadget applications use Relay Cursor style GraphQL pagination, where a second page is fetched by asking for the next x many results after a cursor returned with the first page.
React
1// return the first 10 results after some cursor from somewhere else
7// data is a GadgetRecordList object, which has extra properties for inquiring about the pagination state
8// the current page's start and end cursor are available for use to then make later requests for different pages
9const{
10// string used for forward pagination, pass to the `after:` variable
11 endCursor,
12// string used for backwards pagination, pass to the `before:` variable
13 startCursor,
14
15// `data` also reports if there are more pages for fetching
16// boolean indicating if there is another page to fetch after the `endCursor`
17 hasNextPage,
18// boolean indicating if there is another page to fetch before the `startCursor`
19 hasPreviousPage,
20}= data;
An easy way to do pagination is using React state, or for a better user experience, using the URL with whatever router system works for your application. We use React state to demonstrate pagination in this example:
14return<spanclassName="banner">Check out our most recent blog post titled {data?.title}</span>;
15};
Parameters
manager: The model manager for the model you want to find a page of records for. Required. Example: api.widget, or api.shopifyProduct
options: Options for making the call to the backend. Not required and all keys are optional.
select: A list of fields and subfields to select. See the select option docs. Optional.
filter: A list of filters to find a record matching. Optional. See the Model Filtering section in your application's API documentation to see the available filters for your models.
search: A search string to find a record matching. Optional. See the Model Searching section in your application's API documentation to see the available search syntax.
sort: A sort order to order the backend records by. useFindFirst will only return the first record matching the given search and filter, so sort can be used to break ties and select a specific record. Optional. See the sorting section in your application's API documentation for more info.
live: Should this hook re-render when data changes on the backend. See the live option docs.
requestPolicy: The urql request policy to make the request with. See urql's docs
pause: Should the hook make a request right now or not. See urql's docs
suspense: Should this hook suspend when fetching data. See suspense for more info
Returns
useFindFirst returns two values: a result object with the data, fetching, and error keys for inspecting in your React component's output, and a refetch function to trigger a refresh of the hook's data.
data: GadgetRecord | null: The record fetched from the backend. Is null while the data is being loaded, or if a matching record wasn't found.
fetching: boolean: A boolean describing if the hook is currently making a request to the backend.
error: Error | null: An error from the client or server side, if encountered during the request. Will contain an error if the first record isn't found. See the errors section.
If no record is found matching the conditions, useFindFirst will return {data: null, error: new MissingDataError}.
Without any options, useFindFirst will fetch the first matching record and cause your component to rerender as the fetch happens and when the data or error arrives.
useFindFirst can only select some of the fields from the backend model with select:
React
1// fetch the first upside down widget, and only it's id and name fields
2const[{ data }]=useFindFirst(api.widget,{
3 filter:{
4 state:{ equals:"upsideDown"},
5},
6 select:{
7 id:true,
8 name:true,
9},
10});
1// fetch the first upside down widget, and only it's id and name fields
2const[{ data }]=useFindFirst(api.widget,{
3filter:{
4state:{equals:"upsideDown"},
5},
6select:{
7id:true,
8name:true,
9},
10});
useFindFirst can subscribe to changes in the returned data from the backend with the live option, and re-render when the backend data changes:
React
1// fetch the first upside down widget, and re-render if it's data changes
2const[{ data }]=useFindFirst(api.widget,{
3 filter:{
4 state:{ equals:"upsideDown"},
5},
6 live:true,
7});
1// fetch the first upside down widget, and re-render if it's data changes
useFindBy fetches one record from your backend looked up by a specific field and value. useFindBy requires a by-field record finder like .findBySlug or .findByEmail to exist for your model, which are generated by adding a Unique Validations to a field.
React
1importReactfrom"react";
2import{ useFindBy }from"@gadgetinc/react";
3import{ api }from"../api";
4
5// get a slug from the URL or similar, and look up a post record by this slug
findFunction: The model finder function from your application's API client for finding records by a specific field. Gadget generates these finder functions for the fields where they are available. Changes to your Gadget backend schema may be required to get these to exist. Required. Example: api.widget.findBySlug, or api.user.findByEmail.
fieldValue: The value of the field to search for a record using. This is which slug or email you'd pass to api.widget.findBySlug or api.user.findByEmail.
options: Options for making the call to the backend. Not required and all keys are optional.
select: A list of fields and subfields to select. See the select option docs.
live: Should this hook re-render when data changes on the backend. See the live option docs.
requestPolicy: The urql request policy to make the request with. See urql's docs
pause: Should the hook make a request right now or not. See urql's docs
suspense: Should this hook suspend when fetching data. See suspense for more info
Returns
useFindBy returns two values: a result object with the data, fetching, and error keys for inspecting in your React component's output, and a refetch function to trigger a refresh of the hook's data.
data: GadgetRecord | null: The record fetched from the backend. Is null while the data is being loaded, or if a matching record wasn't found for the given fieldValue.
fetching: boolean: A boolean describing if the hook is currently making a request to the backend.
error: Error | null: An error from the client or server side, if encountered during the request. Will contain an error if a matching record isn't found. See the errors section.
If no record is found matching the conditions, then the returned object will have null for the data. useFindBy(api.widget.findByEmail, "[email protected]") is the React equivalent of api.widget.findByEmail("[email protected]")
Without any options, useFindBy will fetch the record with the given field value, and cause your component to rerender as the fetch happens and when the data or error arrives:
React
1importReactfrom"react";
2import{ useFindBy }from"@gadgetinc/react";
3import{ api }from"../api";
4
5// get a slug from the URL or similar, and look up a post record by this slug
The refetch function returned as the second element can be executed in order to trigger a refetch of the most up to date data from the backend. See urql's docs on re-executing queries for more information.
15return<spanclassName="banner">Check out our most recent blog post titled {data.title}</span>;
16}else{
17// no first record found
18returnnull;
19}
20};
useMaybeFindFirst returns data: null if no record is found in the backend database, and otherwise works identically to useFindFirst. See useFindFirst for more details on the options useMaybeFindFirst accepts.
useAction is a hook for running a backend action on one record of a Gadget model. useAction must be passed an action function from an instance of your application's generated API client. Options:
Parameters
actionFunction: The model action function from your application's API client for acting on records. Gadget generates these action functions for each action defined on backend Gadget models. Required. Example: api.widget.create, or api.user.update or api.blogPost.publish.
options: Options for making the call to the backend. Not required and all keys are optional.
select: A list of fields and subfields to select. See the select option docs.
requestPolicy: The urql request policy to make the request with. See urql's docs
pause: Should the hook make a request right now or not. See urql's docs
suspense: Should this hook suspend when fetching data. See suspense for more info
Returns
useAction returns two values: a result object with the data, fetching, and error keys for inspecting in your React component's output, and a act function to actually run the backend action. useAction is a rule-following React hook that wraps action execution, which means it doesn't just run the action as soon as the hook is invoked. Instead, useAction returns a configured function that will actually run the action, which you need to call in response to some user event. The act function accepts the action inputs as arguments -- not useAction itself.
useAction's result will return the data, fetching, and error details for the most recent execution of the action.
data: GadgetRecord | null: The record fetched from the backend after a mutation. Is null while before the mutation is run and while it is currently ongoing.
fetching: boolean: A boolean describing if the hook is currently making a request to the backend.
error: Error | null: An error from the client or server side, if encountered during the mutation. Will contain an error if the client passed invalid data, if the server failed to complete the action, or if a network error was encountered. See the errors section.
For example, we can create a button that creates a post when clicked, and then shows the post once it has been created:
globalActionFunction: The action function from your application's API client. Gadget generates these global action functions for each global action defined in your Gadget backend. Required. Example: api.runSync, or api.purgeData (corresponding to Global Actions named Run Sync or Purge Data).
options: Options for making the call to the backend. Not required and all keys are optional.
requestPolicy: The urql request policy to make the request with. See urql's docs
pause: Should the hook make a request right now or not. See urql's docs
Returns
useGlobalAction returns two values: a result object with the data, fetching, and error keys for inspecting in your React component's output, and an act function to actually run the backend global action. useGlobalAction is a rule-following React hook that wraps action execution, which means it doesn't just run the action as soon as the hook is invoked. Instead, useGlobalAction returns a configured function which you need to call in response to some event. This act function accepts the action inputs as arguments. useGlobalAction's result will return the data, fetching, and error details for the most recent execution of the action.
data: Record<string, any> | null: The data returned by the global action from the backend. Is null while before the mutation is run and while it is currently ongoing.
fetching: boolean: A boolean describing if the hook is currently making a request to the backend.
error: Error | null: An error from the client or server side, if encountered during the mutation. Will contain an error if the client passed invalid data, if server failed to complete the mutation, or if a network error was encountered. See the errors section.
For example, we can create a button that runs a Global Action called purgeData when clicked, and shows the result after it has been run:
useGet fetches a singleton record for an api.currentSomething style model manager. useGet fetches one global record, which is most often the current session.
If you'd like to access the current session on the frontend, use the useSession() hook
singletonModelManager: The singleton model manager available on the generated API client for your application. The passed model manager must be one of the currentSomething model managers. useGet can't be used with other model managers that don't have a .get function. Example: api.currentSession.
options: Options for making the call to the backend. Not required and all keys are optional.
select: A list of fields and subfields to select. See the select option docs.
requestPolicy: The urql request policy to make the request with. See urql's docs
pause: Should the hook make a request right now or not. See urql's docs
suspense: Should this hook suspend when fetching data. See suspense for more info
Returns
useGet returns two values: a result object with the data, fetching, and error keys for inspecting in your React component's output, and a refetch function to trigger a refresh of the hook's data.
data: GadgetRecord | null: The record fetched from the backend. Is null while the data is being loaded, or if the record wasn't found.
fetching: boolean: A boolean describing if the hook is currently making a request to the backend.
error: Error | null: An error from the client or server side, if encountered during the request. Will contain an error if the singleton record isn't found. See the errors section.
useGet(api.currentSession) retrieves the current global session for the current browser
The refetch function returned as the second element can be executed to trigger a refetch of the most up-to-date data from the backend. See urql's docs on re-executing queries for more information.
useActionForm manages form state for calling actions in your Gadget backend. useActionForm can fetch the record for editing, manage the state of the fields as the user changes them in a form, track validations and errors, and then call the action with the form data when the user submits the form. useActionForm can call Actions on models as well as Global Actions.
useActionForm wraps the excellent react-hook-form library and provides all the same state management
primitives that react-hook-form does, in addition to Gadget-specific goodies like automatic record fetching, automatic action calling
and type safety.
action: the Model Action or Global Action to call when submitting. Required.
options: the configuration for the form
The options options object accepts the following options:
Name
Type
Description
defaultValues
Partial<ActionInput>
Default values to seed the form inputs with. Can be omitted. Mutually exclusive with the findBy. option.
findBy
string or { [field: string]: any }
Details for automatically finding a record to seed the form values with. When passed as a string, will look up a record with that id. When passed an object, will call a findBy<Field> function on the api object to retrieve a record by that field. The field must have a uniqueness validation in order to function.
mode
"onChange" or "onBlur" or "onSubmit" or "onTouched" or "all"
Default options to use when calling reset. For more details, see the reset function docs
criteriaMode
"firstError" or "all"
Display all validation errors or one at a time.
shouldFocusError
boolean
Enable or disable built-in focus management.
delayError
number
Delay errors by this many milliseconds to avoid them appearing instantly
shouldUseNativeValidation
boolean
Use browser built-in form constraint API.
shouldUnregister
boolean
Enable and disable input unregister after unmount.
select
RecordSelection
Which fields to select from the backend when retrieving initial data with findBy. Can also mark fields as ReadOnly to exclude them from being sent during an update. See docs on the select option for more information.
send
string[]
Which fields to send from the form values to the backend for the action. Useful if you want to include fields in your form state for driving UI that shouldn't be sent with the submission
onSubmit
() => void
Callback called right before data is submitted to the backend action
onSuccess
(actionResult: ActionResultData) => void
Callback called after a successful submission to the backend action. Passed the action result, which is the object with {data, error, fetching} keys
onError
(error: Error | FieldErrors) => void
Callback called after an error occurs finding the initial record or during submission to the backend action. Passed the error, which can be a transport error from a broken network, or a list of validation errors returned by the backend
useActionForm's props input is very similar to useForm's from react-hook-form. For more docs on these props, see the react-hook-form docs.
Returns
useActionForm returns a variety of functions and state for managing your form that most users destructure as they call it:
Current state of the form, like validations, errors, submission details, etc docs
submit
(event?: React.Event) => Promise<ActionResult>
A function to call that submits the form to the backend. Returns a promise for the ActionResult object containing the {data, error, fetching} triple returned by the backend action.
Function for returning the state of one individual field from within the form state. docs
trigger
(name?: string | string[]) => Promise<boolean>
Manually triggers form or input validation. This method is also useful when you have dependant validation (input validation depends on another input's value). docs
control
FormControl
Context object for passing to <Controller/> components wrapping ref-less or controlled components
error
Error | null
Any top-level Error objects encountered during processing. Will contain transport level errors as well as field validation errors returned by the backend. This value is for deeply inspecting the error if you want more than just the message, but the formState.errors object should be preferred if not.
The ActionResult triple returned by the inner useAction hook. Will be populated with the action execution result after submission.
FormState object
The FormState object returned by useActionForm includes the following properties:
Name
Type
Description
isDirty
boolean
true if the user has modified any inputs away from the defaultValues, and false otherwise
dirtyFields
Record<string, boolean>
A map of fields to the dirty state for each field. Each field's property on the object true if the user has modified this field away from the default and false otherwise
touchedFields
Record<string, boolean>
A map of fields to the touched state for each field. Each field's property on the object true if the user has modified this field at all and false otherwise
defaultValues
Record<string, any>
The default values the form started out with, or has been reset to
isSubmitted
boolean
true if the form has ever been submitted, false otherwise
isSubmitSuccessful
boolean
true if the form has completed a submission that encountered no errors, false otherwise
isSubmitting
boolean
true if the form is currently submitting to the backend, false otherwise
isLoading
boolean
true if the form is currently loading data from the backend to populate the initial values or another input, false otherwise
submitCount
number
Count of times the form has been submitted
isValid
boolean
true if the form has no validation errors currently, false otherwise
isValidating
boolean
true if the form is currently validating data, false otherwise
errors
Record<string, string>
A map of any validation errors currently present on each field
The FormState object managed by useActionForm (and react-hook-form underneath) is a Proxy object that tracks which properties are
accessed during rendering to avoid excessive re-renders. Make sure you read its properties within a component render function to properly track which properties should trigger re-renders.
Unlike react-hook-form, useActionForm manages the submission process to your backend action. You don't need to manually make a call to your action -- instead, call the submit function returned by useActionForm when you are ready to submit the form, and useActionForm will call the action.
Because the submission process is managed, useActionForm does not accept the handleSubmit option that react-hook-form does.
<Controller/>
useActionForm's register function only works with uncontrolled components that conform to normal DOM APIs. For working with controlled components, like those from popular UI libraries such as @shopify/polaris, you must register these input components with a <Controller/> instead.
The key of this input's data within your form's field values
control
FormControl
Context object returned by useActionForm, must be passed to each <Controller/> to tie them to the form
render
(props: ControllerProps) => ReactElement
A function that returns a React element and provides the ability to attach events and value into the component. This simplifies integrating with external controlled components with non-standard prop names. Provides onChange, onBlur, name, ref and value as props for sending to the child component, and also a fieldState object which contains specific input state.
defaultValue
unknown
A default value for applying to the inner input.
rules
object
Validation options for applying to the form value. Accepts the same format of options as the register function.
shouldUnregister
boolean
Should this input's values/validations/errors be removed on unmount.
disabled
boolean
Is this input currently disabled such that it can't be edited
Update input at a particular position. The updated fields will get unmounted and remounted, if this is not the desired behavior, use setValue API instead
replace
(obj: object[]) => void
Replace all values currently in the field array
remove
(index?: number | number[]) => void
Remove input at a particular position or remove all when no index provided
useList handles the logic of creating a paginated, searchable list of records from your Gadget backend. The useList hook takes the same parameters as useFindMany (with the addition of the pageSize param). Refer to useFindMany for examples of how to query the data that will populate your list.
Parameters
manager: The model manager for the model you want to find a page of records for. Required. Example: api.widget, or api.shopifyProduct
options: Options for making the call to the backend. Not required and all keys are optional.
select: A list of fields and subfields to select. See the select option docs.
filter: A list of filters to limit the set of returned records. Optional. See filtering in your application's API documentation for more info.
search: A search string to match backend records against. Optional. See the model searching section in your application's API documentation for the available search syntax.
sort: A sort order to return backend records by. Optional. See sorting in your application's API documentation for more info.
first & after: Pagination arguments to pass to fetch a subsequent page of records from the backend. first should hold a record count and after should hold a string cursor retrieved from the pageInfo of the previous page of results. See the pagination section in your application's API documentation for more info.
last & before: Pagination arguments to pass to fetch a subsequent page of records from the backend. last should hold a record count and before should hold a string cursor retrieved from the pageInfo of the previous page of results. See the pagination section in your application's API documentation for more info.
live: Should this hook re-render when data changes on the backend. See the live option docs.
requestPolicy: The urql request policy to make the request with. See urql's docs.
pause: Should the hook make a request right now or not. See urql's docs.
suspense: Should this hook suspend when fetching data. See suspense for more info.
pageSize: The page size of the paginated data. Optional, defaults to 50.
Returns
useList returns two values: a result object with the data, fetching, page, search, and error keys for use in your React component's output, and a refresh function to trigger a refresh of the hook's data.
data: GadgetRecord | null: The record fetched from the backend. Is null while the data is being loaded, or if the record wasn't found.
fetching: boolean: A boolean describing if the hook is currently requesting data from the backend.
page: PaginationResult: A collection of variables and functions to handle pagination.
page.hasNextPage: boolean | undefined: Whether the paginated data has a next page.
page.hasPreviousPage: boolean | undefined: Whether the paginated data has a previous page.
first holds a record count and after holds a string cursor retrieved from the pageInfo of the previous page of results. See the pagination section in your application's API documentation for more info.
last holds a record count and before holds a string cursor retrieved from the pageInfo of the previous page of results. See the pagination section in your application's API documentation for more info.
page.pageSize: number: Page size of the paginated data. Defaults to 50.
page.goToNextPage: () => void: Function to load the next page of paginated data.
page.goToPreviousPage: () => void: Function to load the last page of paginated data.
search: SearchResult: A collection of variables and functions to handle pagination.
value: string: The current value of the input, possibly changing rapidly as the user types.
debouncedValue: string: The value that has been processed by the debounce function, updating less frequently than value. Learn more about debouncing.
set: (value: string) => void: A function to update the value.
clear: () => void: A function to clear the value.
error: Error | null: An error from the client or server side, if encountered during the request. Will contain an error if the record isn't found by id. See the errors section.
Paginated list
Here's how you can create a paginated list that is synced with your data in Gadget:
pagination example with useList
React
1import{ useList }from"@gadgetinc/react";
2// your app's auto-generated API client
3import{ api }from"../api";
4
5exportconstPaginatedList=()=>{
6// Passing the same filter/sort/search params to useList as useFindMany:
useTable is a headless React hook for powering a table. The table shows a page of Gadget records from the backend. The hook returns an object with optional params for sorting, filtering, searching, and data selection. useTable returns an object with data, fetching, and error keys, and a refetch function. data is a GadgetRecordList object holding the list of returned records and pagination info.
This hook is like useList. The difference is it divides each field into columns, and orders the records into rows.
manager: The model manager for the model you want to find a page of records for. Required. Example: api.widget, or api.shopifyProduct
options: Options for making the call to the backend. Not required and all keys are optional.
select: A list of fields and subfields to select. See the select option docs.
filter: A list of filters to limit the set of returned records. Optional. See the model filtering section in your application's API documentation to see the available filters for your models.
search: A search string to match backend records against. Optional. See the model searching section in your application's API documentation to see the available search syntax.
live: Should this hook re-render when data changes on the backend. See the live option docs.
requestPolicy: The urql request policy to make the request with. See urql's docs
pause: Should the hook make a request right now or not. See urql's docs
suspense: Should this hook suspend when fetching data. See suspense for more info
pageSize: The page size of the paginated data. Optional, defaults to 50.
initialCursor: A string cursor; useTable handles pagination, so this prop is only needed if you get the cursor hash from the returned after or before variables, and want to set the cursor to a custom spot.
initialSort: An object of type { [column: string]: "Ascending" | "Descending" } that sets the initial sort order for the table.
initialDirection: Initial pagination direction. Either "forward" or "backward".
columns: A list of field API identifiers and custom column renderer objects to be returned. Custom cell renderers have type {header: string; render: (props: {record: GadgetRecord<any>, index: number}) => ReactNode; style?: React.CSSProperties;}
columns prop example
React
// Only returns the `name` and `createdAt` columns
rows: Record<string, ColumnValueType>[]: A list of records indexed by each column's API identifier. If the column displays a field of type number, then the ColumnValueType type will take on the number type.
columns: RecordTableColumnValue[]: columns is a list of objects with the following attributes:
identifier: string: The identifier of the field. For Gadget fields, this is the field's API identifier. For custom columns, this is a UUID.
header: string: The header of the column. If the current column does not have a custom configuration, the Gadget field's name will be used.
field: string: The field's API identifier. For Gadget relationship fields, this is the dot separated path to the displayed field on the related model.
type: string: The field type (string, number, json, etc) of the displayed value
relationshipType?: string: The parent field type for relationship fields (belongs to, has one, has many, has many through). The type of the displayed value is represented in type.
sortable: boolean: Whether the column can be sorted.
includeTime?: boolean: true when the field is a date / time field with includeTime enabled.
render: (props: {record: GadgetRecord<any>, index: number}) => ReactNode: Given a record and the row index, render returns the ReactNode that will render in the table's cell.
style?: React.CSSProperties: A CSS style object for the current column forwarded from from the corresponding column entry in the columns option in useTable.
metadata: ModelMetadata: An array of objects that describe each field in the model.
example ModelMetadata object
json
1[
2{
3"name":"Id",
4"apiIdentifier":"id",
5"fieldType":"ID",
6"requiredArgumentForInput":true,
7"sortable":true,
8"filterable":true,
9"__typename":"GadgetModelField",
10"configuration":{
11"__typename":"GadgetGenericFieldConfig",
12"fieldType":"ID",
13"validations":[
14{
15"__typename":"GadgetGenericFieldValidation",
16"name":"Uniqueness",
17"specID":"gadget/validation/unique"
18},
19{
20"__typename":"GadgetGenericFieldValidation",
21"name":"Required",
22"specID":"gadget/validation/required"
23}
24]
25}
26}
27]
fetching: boolean: A boolean describing if the hook is currently requesting data from the backend.
page: PaginationResult: A collection of variables and functions to handle pagination.
page.hasNextPage: boolean | undefined: Whether the paginated data has a next page.
page.hasPreviousPage: boolean | undefined: Whether the paginated data has a previous page.
first holds a record count and after holds a string cursor retrieved from the pageInfo of the previous page of results. See the pagination section in your application's API documentation for more info.
last holds a record count and before holds a string cursor retrieved from the pageInfo of the previous page of results. See the pagination section in your application's API documentation for more info.
page.pageSize: number: Page size of the paginated data. Defaults to 50.
page.goToNextPage: () => void: Function to load the next page of paginated data.
page.goToPreviousPage: () => void: Function to load the last page of paginated data.
search: SearchResult: A collection of variables and functions to handle pagination.
value: string: The current value of the input, possibly changing rapidly as the user types.
debouncedValue: string: The value that has been processed by the debounce function, updating less frequently than value. Learn more about debouncing.
set: (value: string) => void: A function to update the value.
clear: () => void: A function to clear the value.
sort: (colName: string, sortDirection: "Ascending" | "Descending") => void: A function that sorts by column name. If sort is undefined, no sorting is applied to the table.
error: Error | null: An error from the client or server side, if encountered during the request. Will contain an error if the record isn't found by id. See the errors section.
Paginated table
useTable handles pagination in the same way as the useList hook.
useTable returns a search object that allows you to search through the first page of data returned by the hook. Simply set the search value to the user's search query, and the table will automatically rerender:
useFetch is a low-level hook for making an HTTP request to your Gadget backend's HTTP routes. useFetch preserves client-side authentication information by using api.fetch under the hood, which means fetches will use the same request identity as other GraphQL API calls using the other hooks.
Gadget apps get an auto-generated API for reading and writing data to your models, which is often faster and easier to use than
useFetch. See your app's API reference for
more information.
14if(!data)return<>No user found with id={props.id}</>;
15
16return<div>{data.name}</div>;
17}
Parameters
path: the server-side URL to fetch from. Corresponds to an HTTP route defined on in your backend Gadget app's routes folder
options: options configuring the fetch call, corresponding exactly to those you might send with a normal fetch.
method: the request method, like "GET", "POST", etc. Defaults to "GET"
headers: the request headers, like { "content-type": "application/json" }
body: the request body to send to the server, like "hello" or JSON.stringify({foo: "bar"})
json: If true, expects the response to be returned as JSON, and parses it for convenience
stream:
If true, response will be a ReadableStream object, allowing you to work with the response as it arrives
If "string", will decode the response as a string and update data as the response arrives; this is useful when streaming responses from LLMs
onStreamComplete: a callback function that will be called with the final content when the streaming response is complete; this is only available when the stream: "string" option is set
sendImmediately: If true, sends the first fetch on component mount. If false, waits for the send function to be called to send a request. Defaults to true for GET requests and false for any other HTTP verbs.
useFetch returns a tuple with the current state of the request and a function to send or re-send the request. The state is an object with the following fields:
data: the response data, if the request was successful
fetching: a boolean describing if the fetch request is currently in progress
streaming: a boolean describing if the fetch request is currently streaming. This is only set when the option { stream: "string" } is set
error: an error object if the request failed in any way
The second return value is a function for sending or resending the fetch request.
Request method
By default, GET requests are sent as soon as the hook executes. GET requests can also be refreshed by calling the second return value to re-send the fetch request and fetch fresh data.
React
1// GET request will be sent immediately, can be refreshed by calling `send()` again
Other request methods like POST, DELETE, etc will not be sent automatically. The request will only be sent when the send functions is called explicitly, often in a click handler or similar.
React
1// POST requests will not be sent until `send` is called explicitly
useFetch supports sending data to the server in the request body using the body option. Bodies are only supported for HTTP verbs which support them, like POST, PUT, PATCH, and DELETE.
To send a request body, pass a string, Buffer, or Stream object in the body key, and set the content-type header to match the type of data you are sending.
This will send your data to a backend routes/some/POST-path.js file, where request.body will be { foo: "bar" }.
Parsing the response
Unlike the useFind hooks, useFetch doesn't automatically parse and return rich data from your HTTP route. By default, useFetch returns a string of the response for the data. But, there's a couple convenience options for quickly parsing the response into the shape you need.
Pass the { json: true } option to expect a JSON response from the server, and to automatically parse the response as JSON.
Pass the { stream: true } to get a ReadableStream object as a response from the server, allowing you to work with the response as it arrives. Otherwise, the response will be returned as a string object.
Pass the { stream: "string" } to decode the ReadableStream as a string and update data as it arrives. If the stream is in an encoding other than utf8 pass the encoding i.e. { stream: "utf-16" }. When { stream: "string" } is used, the streaming field in the state will be set to true while the stream is active, and false when the stream is complete. You can use this to show a loading indicator while the stream is active. You can also pass an onStreamComplete callback that will be called with the final string content when the stream is complete.
When possible, the hooks which make requests to your structured GraphQL API should be preferred. Your app's GraphQL API is auto-generated and full of useful features, which means you don't need to wire up custom routes on your backend to serve data. The API hooks provide built in type safety, error handling, caching, and useFetch does not.
Calling third-party APIs with useFetch
@gadgetinc/react's useFetch hook calls fetch under the hood both client side and server side, which means you can use it to make HTTP requests to services other than your Gadget backend. You don't have to use useFetch to make calls elsewhere, but it is handy for avoiding adding other dependencies to your frontend code.
For example, we can call a third-party JSON API at dummyjson.com:
useFetch will not send your Gadget API client's authentication headers to third party APIs. It will behave like a normal browser fetch call, just with the added React wrapper and json: true option for easy JSON parsing.
When the request gets sent
By default, useFetch will immediately issue HTTP requests for GETs when run. This makes it easy to use useFetch to retrieve data for use rendering your component right away.
React
1import{ useFetch }from"@gadgetinc/react";
2
3exportfunctionGetRequest(){
4// will automatically send the request when the component renders the first time, as it is a GET
useFetch will not immediately issue HTTP requests for HTTP verbs other than GET, like POST, PUT, etc. The HTTP request will only be sent when you call the returned send function.
React
1import{ useFetch }from"@gadgetinc/react";
2
3exportfunctionPostRequest(){
4// will not automatically send the request when the component renders, call `send` to issue the request
user - the current User, if signed in. Similar to useUser.
session - the current Session. Similar to useSession.
isSignedIn - set to true if the session has a user associated with it (signed in), false otherwise.
The select option
The select option allows you to choose which fields and subfields are returned by your Gadget app's GraphQL API. Your app's API supports returning only some fields of each model you request, as well as fields of related models through the Gadget relationship field types. The select option is an object with keys representing the apiIdentifier of fields in your Gadget models, and values holding a boolean describing if that field should be selected or not, or a subselection for object-typed fields.
For example, you can limit the fields selected by a finder to only return some fields, lowering the amount of bandwidth used and making your requests faster:
You can also use the select option for selecting fields of related models. For example, if we have a backend Blog Post model which has a HasMany field to a Comment model, we can fetch a blog post and it's related comments:
11// and fetch the post's `comments` HasMany relationship field on the post
12comments:{
13edges:{
14node:{
15id:true,
16body:true,
17// and fetch the author's BelongsTo User relationship field also
18author:{email:true},
19},
20},
21},
22},
23});
24
25if(!data)returnnull;
26return(
27<>
28<h2>{data.title}</h2>
29<ul>
30{data.comments.edges.map((edge)=>(
31<li>
32{edge.node.author?.email} says {edge.node.body}
33</li>
34))}
35</ul>
36</>
37);
38};
Note: The shape of the options you pass in the select option matches exactly the shape of the GraphQL API for your application. Gadget applications use Relay-style GraphQL pagination, which means lists of records are accessed using the relatedField: { edges: { node: true } } style. BelongsTo and HasOne field types are accessed without any intermediate fields.
For TypeScript users, the select option is fully typesafe, allowing you to typecheck which fields you're fetching from the backend as well as ensure that the fields you render in your components are actually selected.
The select option for useActionForm
The select option for useActionForm is slightly different from the select option for other actions. For useActionForm, the select option allows you to mark fields as ReadOnly to indicate that they should not be forwarded to the backend when submitting the form. For information, see the useActionForm guide.
The live option makes your component re-render when the data it is showing changes for any reason in the database. Passing live: true sets up a special @live query from your frontend to the Gadget backend which subscribes to changes in the on-screen data, and will continue streaming in those changes as they happen while the component remains mounted.
For example, we can show users a live view of the list of widgets from the backend with useFindMany(api.widget, { live: true }):
live: true can be combined with the other options you might pass hooks, like the select option for selecting fields of related models, or the filter and sort options for limiting the result set. Hooks passed live: true will respect the given selection, filtering, sorting, and pagination, and only trigger re-renders when the relevant backend data changes.
11// fetch the post's `comments` HasMany relationship field on the post
12comments:{
13edges:{
14node:{
15id:true,
16body:true,
17// fetch the author's BelongsTo User relationship field also
18author:{
19email:true,
20},
21},
22},
23},
24},
25});
26
27if(!data)returnnull;
28// will re-render when the blog post changes, any of its comments change, or any of the comment authors' emails change
29return(
30<>
31<h2>{data.title}</h2>
32<ul>
33{data.comments.edges.map((edge)=>(
34<li>
35{edge.node.author?.email} says {edge.node.body}
36</li>
37))}
38</ul>
39</>
40);
41};
Live query result values
When using live: true, your hook will the same thing the non-live variants do, which is a tuple with:
a data object containing the up-to-date result from the backend
a fetching boolean describing if the initial data fetch has completed or not
an error object describing any errors encountered during execution at any point
When the live: true hook mounts, it will fetch some initial data, then keep it up to data over time by subscribing to the backend. The fetching boolean describes if the initial data fetch has happened. Once the initial fetch is complete, the fetching boolean will be false, and new data will appear in the data object.
Errors from the returned error object
Running queries or mutations can produce a few different kinds of errors your client side should handle:
network errors where the browser is unable to connect to the server at all
validation errors where the client sent information to the server successfully, but the server deemed it invalid and rejected it
server side errors where the client sent information to the server but the server failed to process it due to a bug or transient issue.
Each of these error cases is broken out on the error object returned by useAction (and any of the other hooks). The error object is an ErrorWrapper object, which has a number of properties for figuring out exactly what went wrong:
error.message: string - A top level error message which is always present
error.networkError: Error | undefined - An error thrown by the browser when trying to communicate with the server
error.executionErrors: (GraphQLError | GadgetError)[] | undefined - Any errors thrown by the GraphQL API, like missing parameters or invalid selections, and any errors thrown by the server concerning invalid data or backend processing errors.
error.validationErrors: { apiIdentifier: string, message: string }[] | undefined - Any validation errors returned by the server. A shortcut to accessing the .validationErrors property of the first InvalidRecordError in the .executionErrors of the outer ErrorWrapper object. Useful for building form validations.
Default selections
Gadget makes a default selection when you don't pass the select option to a finder, which will include all the model's scalar fields and a small representation of its related records. This default is also type safe, so you can rely on the returned objects from default finder methods returning type safe results conforming to the default shape. To figure out exactly what your client will select by default for a model, see the documentation for that model in your generated API documentation.
The refetch function
The refetch function returned as the second return value for some hooks can be executed in order to trigger a refetch of the most up to date data from the backend. This is useful for powering refresh buttons in user-facing UI, or for periodically updating the client side data. See urql's docs on re-executing queries for more information.
As an example, we could use the refetch function to power a refresh button in a table:
React
1importReactfrom"react";
2import{ useFindMany }from"@gadgetinc/react";
3import{ api }from"../api";
4
5exportconstShowWidgetNames=()=>{
6// get the second return value of `useFindMany`, which is the refetch function
@gadgetinc/react supports two modes for managing loading states: the fetching return value, which will be true when making requests under the hood, as well as using <Suspense/>, React's next generation tool for managing asynchrony. Read more about <Suspense/> in the React docs.
To suspend rendering when fetching data, pass the suspense: true option to the useFind* hooks.
React
1importReactfrom"react";
2import{ useFindMany }from"@gadgetinc/react";
3import{ api }from"../api";
4
5exportconstPosts=()=>{
6// pass suspense: true, and the component will only render once data has been returned
All the read hooks support suspense: useFindOne, useMaybeFindOne, useFindMany, useFindFirst, useMaybeFindFirst, and useGet.
suspense: true is most useful when a parent component wraps a suspending-child with the <Suspense/> component for rendering a fallback UI while the child component is suspended:
React
1constPostsContainer=()=>{
2return(
3<Suspensefallback={"loading..."}>
4<Posts/>
5</Suspense>
6);
7};
1constPostsContainer=()=>{
2return(
3<Suspensefallback={"loading..."}>
4<Posts/>
5</Suspense>
6);
7};
With this wrapper in place, the fallback prop will be rendered while the data is being fetched, and once it's available, the <Posts/> component will render with data.
Read more about <Suspense/> in the React docs. suspense: true uses urql's suspense support under the hood.
Request caching
Under the hood, your Gadget app's API client and @gadgetinc/react use a powerful, production-grade GraphQL client called urql. urql has a great client-side data caching feature built-in called Document Caching which allows React components issuing GraphQL requests for the same data to de-duplicate requests and share client-side state. @gadgetinc/react enables this functionality by default.
@gadgetinc/react runs urql's Document Caching with a default requestPolicy of cache-and-network, which means your React hooks will re-render data with any cached results from the in-memory store, and then make an underlying HTTP request to fetch the most up to date data.
If you want to change the default requestPolicy that your Gadget API client and React hooks use, you can pass the requestPolicy option to your API client constructor.
React
// instantiate the API client for our app that will make network calls for every query, regardless of cache state
const api =newClient({
requestPolicy:"network-only",
});
// instantiate the API client for our app that will make network calls for every query, regardless of cache state
const api =newClient({
requestPolicy:"network-only",
});
There are four different request policies that you can use:
cache-first prefers cached results and falls back to sending an API request when no prior result is cached.
cache-and-network (the default) returns cached results but also always sends an API request, which is perfect for displaying data quickly while keeping it up-to-date.
network-only will always send an API request and will ignore cached results.
cache-only will always return cached results or null.
For more information on urql's built-in client-side caching, see urql's docs.
urql exports
Since this library uses urql behind the scenes, it provides a few useful exports directly from urql so that it does not need to be installed as a peer dependency should you need to write custom queries or mutations.
If you are trying to control the layout of your application based on authentication state, it may be helpful to use the Gadget auth React components instead of, or in addition to, the hooks.
<SignedIn />
Conditionally renders its children if the current session has a user associated with it, similar to the isSignedIn property of the useAuth() hook.
React
1import{SignedIn}from"@gadgetinc/react";
2
3constSignedInMessage=()=>(
4<h1>
5 Hello<SignedIn>, human</SignedIn>!
6</h1>
7);
1import{SignedIn}from"@gadgetinc/react";
2
3constSignedInMessage=()=>(
4<h1>
5 Hello<SignedIn>, human</SignedIn>!
6</h1>
7);
<SignedOut />
Conditionally renders its children if the current session does not have a user associated with it.
React
1import{SignedOut}from"@gadgetinc/react";
2
3constSignedOutMessage=()=>(
4<SignedOut>
5<ahref="/auth/signin">Sign In!</a>
6</SignedOut>
7);
1import{SignedOut}from"@gadgetinc/react";
2
3constSignedOutMessage=()=>(
4<SignedOut>
5<ahref="/auth/signin">Sign In!</a>
6</SignedOut>
7);
<SignedInOrRedirect />
Conditionally renders its children if the current session has a user associated with it, or redirects the browser via window.location.assign if the user is not currently signed in. This component is helpful for protecting frontend routes.
Conditionally renders its children if the current Session is signed out, otherwise redirects the browser to the path prop. Uses window.location.assign to perform the redirect.
When working with Gadget auth, there are several hooks and components that can help you manage the authentication state of your application.
The Provider component exported from this library accepts an auth prop which can be used to configure the relative paths to your app's sign in and sign out endpoints. If you do not provide these paths, the default values of / and /signed-in will be used.
The hooks use the Gadget client's suspense: true option, making it easier to manage the async nature of the hooks without having to deal with loading state.