User

This page documents the User model.

Data Shape

Gadget's database stores User records by storing and retrieving each of the fields defined on the model in the Gadget Editor to a managed database. Gadget has generated a GraphQL type matching the configured fields for User:

User Schema
1export interface User {
2 __typename: "User";
3
4 /** The globally unique, unchanging identifier for this record. Assigned and managed by Gadget. */
5 id: Scalars["GadgetID"];
6
7 /** The time at which this record was first created. Set once upon record creation and never changed. Managed by Gadget. */
8 createdAt: Scalars["DateTime"];
9
10 /** The time at which this record was last changed. Set each time the record is successfully acted upon by an action. Managed by Gadget. */
11 updatedAt: Scalars["DateTime"];
12
13 email: Scalars["EmailAddress"] | null;
14
15 roles: Role[];
16
17 sessions: SessionConnection;
18
19 posts: PostConnection;
20
21 /** Get all the fields for this record. Useful for not having to list out all the fields you want to retrieve, but slower. */
22 _all: Scalars["JSONObject"];
23}
1type User {
2 """
3 The globally unique, unchanging identifier for this record. Assigned and managed by Gadget.
4 """
5 id: GadgetID!
6
7 """
8 The time at which this record was first created. Set once upon record creation and never changed. Managed by Gadget.
9 """
10 createdAt: DateTime!
11
12 """
13 The time at which this record was last changed. Set each time the record is successfully acted upon by an action. Managed by Gadget.
14 """
15 updatedAt: DateTime!
16 email: EmailAddress
17 roles: [Role!]
18 sessions(
19 """
20 Returns the items in the list that come after the specified cursor.
21 """
22 after: String
23
24 """
25 Returns the first n items from the list.
26 """
27 first: Int
28
29 """
30 Returns the items in the list that come before the specified cursor.
31 """
32 before: String
33
34 """
35 Returns the last n items from the list.
36 """
37 last: Int
38 ): SessionConnection!
39 posts(
40 """
41 Returns the items in the list that come after the specified cursor.
42 """
43 after: String
44
45 """
46 Returns the first n items from the list.
47 """
48 first: Int
49
50 """
51 Returns the items in the list that come before the specified cursor.
52 """
53 before: String
54
55 """
56 Returns the last n items from the list.
57 """
58 last: Int
59
60 """
61 A list of sort orders to return the results in
62 """
63 sort: [PostSort!]
64
65 """
66 A list of filters to refine the results by
67 """
68 filter: [PostFilter!]
69
70 """
71 A free form text search query to find records matching
72 """
73 search: String
74 ): PostConnection!
75
76 """
77 Get all the fields for this record. Useful for not having to list out all the fields you want to retrieve, but slower.
78 """
79 _all: JSONObject!
80}

You can preview what a real record's shape looks like by fetching it using the blog API Playground.

Any fetched User record will have this same User type, and expose the same data by default, regardless of if it's fetched by ID or as part of a findMany. This means you can select any of the record's fields wherever you like in a GraphQL query according to the use case at hand.

Retrieving one User record

Individual User records can be retrieved using the "find by ID" API endpoint. You can also return only some fields, or extra fields beyond what Gadget retrieves by default, using the select option.

The findOne function throws an error if no matching record is found, which you will need to catch and handle. Alternatively, you can use the maybeFindOne function, which returns null if no record is found, without throwing an error.

Similarly, the useFindOne React hook returns (but does not throw) an error when no matching record is found, while the useMaybeFindOne hook simply returns null if no record is found, without also returning an error.

Get one User
const userRecord = await api.user.findOne("some-id");
console.log(userRecord.id); //=> a string
console.log(userRecord.createdAt); //=> a Date object
const [result, refresh] = useFindOne(api.user, "some-id");
const { data, error, fetching } = result;
console.log(data?.id); //=> a string
console.log(data?.createdAt); //=> a Date object
1query GetOneUser($id: GadgetID!) {
2 user(id: $id) {
3 __typename
4 id
5 createdAt
6 email
7 roles {
8 key
9 name
10 }
11 updatedAt
12 }
13}
Variables
json
{ "id": "some-id" }

Retrieving the first of many User records

The first record from a list of records can be retrieved using the "find first" API endpoint. The source list of records can be filtered using the filter option, sorted using the sort option, searched using the search option, though no pagination options are available on this endpoint. You can also return only some fields, or extra fields beyond what Gadget retrieves by default using the select option.

The findFirst function throws an error if no matching record is found, which you will need to catch and handle. Alternatively, you can use the maybeFindFirst function, which returns null if no record is found, without throwing an error.

Similarly, the useFindFirst React hook returns (but does not throw) an error when no matching record is found, while the useMaybeFindFirst hook simply returns null if no record is found, without also returning an error.

Get one User
const userRecord = await api.user.findFirst();
console.log(userRecord.id); //=> a string
console.log(userRecord.createdAt); //=> a Date object
const [result, refresh] = useFindFirst(api.user);
const { data, error, fetching } = result;
console.log(data?.id); //=> a string
console.log(data?.createdAt); //=> a Date object
1query FindManyUsers(
2 $first: Int
3 $search: String
4 $sort: [UserSort!]
5 $filter: [UserFilter!]
6) {
7 users(first: $first, search: $search, sort: $sort, filter: $filter) {
8 edges {
9 node {
10 __typename
11 id
12 createdAt
13 email
14 roles {
15 key
16 name
17 }
18 updatedAt
19 }
20 }
21 }
22}
Variables
json
{ "first": 1 }

Retrieving many User records

Pages of User records can be retrieved by using the "find many" API endpoint. The returned records can be filtered using the filter option, sorted using the sort option, searched using the search option, and paginated using standard Relay-style pagination options. You can also return only some fields, or extra fields beyond what Gadget retrieves by default using the select option.

This GraphQL endpoint returns records in the Relay Connection style (as a list of edges with nodes and cursors) so they can be paginated. The users GraphQL endpoint works with any Relay-compatible caching client, or you can use Gadget's JS client for pagination with the findMany function.

Find a page of Users

Fetch a page of records with the user.findMany JS method or the users GraphQL field. No options are required. The records returned will be implicitly sorted by ID ascending.

Find many Users
const userRecords = await api.user.findMany();
console.log(userRecords.length); //=> a number
console.log(userRecords[0].id); //=> a string
const [result, refresh] = useFindMany(api.user);
const { data, error, fetching } = result;
console.log(data?.length); //=> a number
console.log(data?.[0].length); //=> a string
1query FindManyUsers {
2 users {
3 edges {
4 node {
5 __typename
6 id
7 # ...
8 createdAt
9 email
10 updatedAt
11 }
12 }
13 }
14}
Variables
json
{}

Retrieving a single User record by a uniquely identifiable field

After adding a unique validation to a field, you can retrieve a single record by using the finders generated below. If you would like to edit the fields returned or filtering, see the filtering section.

Retrieving a single User record by ID

Individual User records can be retrieved using the "find many" API endpoint pre-filtered by the field's ID. Throws if stored data is not unique.

Find Users
const userRecord = await api.user.findById("some-value");
console.log(userRecord.id); //=> a string
const [result, refresh] = useFindBy(api.user.findById, "some-value");
const { data, error, fetching } = result;
console.log(data?.id); //=> a string

Retrieving a single User record by Email

Individual User records can be retrieved using the "find many" API endpoint pre-filtered by the field's Email. Throws if stored data is not unique.

Find Users
const userRecord = await api.user.findByEmail("some-value");
console.log(userRecord.id); //=> a string
const [result, refresh] = useFindBy(api.user.findByEmail, "some-value");
const { data, error, fetching } = result;
console.log(data?.id); //=> a string

Sorting

Records can be sorted in the database to retrieve them in a certain order. Records are always implicitly sorted by ID ascending unless an explicit sort on the id field is defined. The GraphQL type UserSort defines which fields can be sorted by.

Records can be sorted by multiple different fields and in multiple different directions by passing a list of UserSort instead of just one.

GraphQL
1input UserSort {
2 id: SortOrder
3 createdAt: SortOrder
4 updatedAt: SortOrder
5 email: SortOrder
6}

Pass the sort option to the JS client, or the sort variable to a GraphQL query to sort the records returned.

Sort User by most recently created
const userRecords = await api.user.findMany({ sort: { createdAt: "Descending" } });
const [result, refresh] = useFindMany(api.user, {
sort: { createdAt: "Descending" },
});
const { data, error, fetching } = result;
1query FindManyUsers($sort: [UserSort!]) {
2 users(sort: $sort) {
3 edges {
4 node {
5 __typename
6 id
7 # ...
8 createdAt
9 email
10 updatedAt
11 }
12 }
13 }
14}
Variables
json
{ "sort": { "createdAt": "Descending" } }

Sort by multiple fields by passing an array of { [field]: "Ascending" | "Descending" } objects.

Sort User by multiple fields
const userRecords = await api.user.findMany({
sort: [{ state: "Descending" }, { createdAt: "Ascending" }],
});
const [result, refresh] = useFindMany(api.user, {
sort: [{ state: "Descending" }, { createdAt: "Ascending" }],
});
const { data, error, fetching } = result;
1query FindManyUsers($sort: [UserSort!]) {
2 users(sort: $sort) {
3 edges {
4 node {
5 __typename
6 id
7 # ...
8 createdAt
9 email
10 updatedAt
11 }
12 }
13 }
14}
Variables
json
{ "sort": [{ "state": "Descending" }, { "createdAt": "Ascending" }] }

All primitive field types in Gadget are sortable so you are able to sort by fields you have added to a model as well.

Sort Users by ID descending
const userRecords = await api.user.findMany({
sort: { id: "Descending" },
});
const [result, refresh] = useFindMany(api.user, {
sort: { id: "Descending" },
});
const { data, error, fetching } = result;
1query FindManyUsers($sort: [UserSort!]) {
2 users(sort: $sort) {
3 edges {
4 node {
5 __typename
6 id
7 # ...
8 createdAt
9 email
10 updatedAt
11 }
12 }
13 }
14}
Variables
json
{ "sort": { "id": "Descending" } }

Searching

User records can be searched using Gadget's built in full text search functionality. Gadget search is appropriate for powering autocompletes, searchable tables, or other experiences where humans are writing search queries. It's typo tolerant, synonym aware and supports simple search operators like ! to exclude search terms.

Search Users by passing the search parameter with a search query string.

Search isn't field specific in Gadget -- all String or RichText field types are searched with the built in search functionality.

Full text search Users
const userRecords = await api.user.findMany({
search: "a specific phrase to search for",
});
const [result, refresh] = useFindMany(api.user, {
search: "a specific phrase to search for",
});
const { data, error, fetching } = result;
1query FindManyUsers($search: String) {
2 users(search: $search) {
3 edges {
4 node {
5 __typename
6 id
7 # ...
8 createdAt
9 email
10 updatedAt
11 }
12 }
13 }
14}
Variables
json
{ "search": "a specific phrase to search for" }

Filtering

User records can be filtered to return only the appropriate records. Records can be filtered on any field, including those managed by Gadget or fields added by developers. Filters can be combined with sorts, searches and paginated using cursor-based Relay pagination.

Filter Users by passing the filter parameter with a filter object. Filter objects are nestable boolean conditions expressed as JS objects capturing a key, an operator, and usually a value.

The GraphQL type UserFilter defines which fields can be filtered on.

Records can be filtered by multiple different fields. If you want to combine filters using boolean logic, nest them under the AND, OR, or NOT keys of a parent filter. Filters can be nested deeply by passing multiple levels boolean condition filters.

You can also pass a list of filters to the filter parameter which will be implicitly ANDed with one another such that they all need to match for a record to be returned.

Available filters
GraphQL
1input UserFilter {
2 AND: [UserFilter]
3 OR: [UserFilter]
4 NOT: [UserFilter]
5 id: IDFilter
6 createdAt: DateTimeFilter
7 updatedAt: DateTimeFilter
8 state: JSONFilter
9 email: StringFilter
10}
Find Users created in the last day
const yesterday = new Date(Date.now() - 864e5);
const userRecords = await api.user.findMany({
filter: { createdAt: { greaterThan: yesterday } },
});
const yesterday = new Date(Date.now() - 864e5);
const [result, refresh] = useFindMany(api.user, {
filter: { createdAt: { greaterThan: yesterday } },
});
const { data, error, fetching } = result;
1query FindManyUsers($filter: [UserFilter!]) {
2 users(filter: $filter) {
3 edges {
4 node {
5 __typename
6 id
7 # ...
8 createdAt
9 email
10 updatedAt
11 }
12 }
13 }
14}
Variables
json
{ "filter": { "createdAt": { "greaterThan": "2022-11-30T10:43:46.696Z" } } }
Users created this week or updated today
1const yesterday = new Date(Date.now() - 86400000);
2const oneWeekAgo = new Date(Date.now() - 604800000);
3const userRecords = await api.user.findMany({
4 filter: {
5 OR: [
6 {
7 createdAt: { greaterThan: oneWeekAgo },
8 },
9 {
10 updated: { greaterThan: yesterday },
11 },
12 ],
13 },
14});
1const yesterday = new Date(Date.now() - 86400000);
2const oneWeekAgo = new Date(Date.now() - 604800000);
3const [result, refresh] = useFindMany(api.user, {
4 filter: {
5 OR: [
6 {
7 createdAt: { greaterThan: oneWeekAgo },
8 },
9 {
10 updated: { greaterThan: yesterday },
11 },
12 ],
13 },
14});
15const { data, error, fetching } = result;
1query FindManyUsers($filter: [UserFilter!]) {
2 users(filter: $filter) {
3 edges {
4 node {
5 __typename
6 id
7 # ...
8 createdAt
9 email
10 updatedAt
11 }
12 }
13 }
14}
Variables
json
1{
2 "filter": {
3 "OR": [
4 { "createdAt": { "greaterThan": "2022-11-24T10:43:46.696Z" } },
5 { "updated": { "greaterThan": "2022-11-30T10:43:46.696Z" } }
6 ]
7 }
8}
Filter records that are in the created state
const userRecords = await api.user.findMany({
filter: {
state: { inState: "created" },
},
});
1const [result, refresh] = useFindMany(api.user, {
2 filter: {
3 state: { inState: "created" },
4 },
5});
6const { data, error, fetching } = result;
1query FindManyUsers($filter: [UserFilter!]) {
2 users(filter: $filter) {
3 edges {
4 node {
5 __typename
6 id
7 # ...
8 createdAt
9 email
10 updatedAt
11 }
12 }
13 }
14}
Variables
json
{ "filter": { "state": { "inState": "created" } } }

Most field types in Gadget are filterable, so you are able to filter by fields you have added to a model as well.

const userRecords = await api.user.findMany({
filter: {
id: { isSet: true },
},
});
1const [result, refresh] = useFindMany(api.user, {
2 filter: {
3 id: { isSet: true },
4 },
5});
6const { data, error, fetching } = result;
1query FindManyUsers($filter: [UserFilter!]) {
2 users(filter: $filter) {
3 edges {
4 node {
5 __typename
6 id
7 # ...
8 createdAt
9 email
10 updatedAt
11 }
12 }
13 }
14}
Variables
json
{ "filter": { "id": { "isSet": true } } }

Pagination

All Gadget record lists, including the top level User finder as well as associations to User, are structured as GraphQL connections. GraphQL connections are the defacto standard for querying lists and support cursor based forward and backward pagination. When querying via GraphQL, you must select the edges field and then the node field to get the User record. When querying using a Gadget API client, the GraphQL queries are generated for you and the records are unwrapped and returned as a GadgetRecordList ready for use.

User pagination supports the standard GraphQL connection pagination arguments: first + after, or last + before. Pagination is done using cursors, which you can retrieve from the edge.cursor field or the pageInfo.startCursor properties.

Get the first page of 25 Users
const userRecords = await api.user.findMany({ first: 25 });
console.log(userRecords.length); //=> no greater than 25
const [result, refresh] = useFindMany(api.user, { first: 25 });
const { data, error, fetching } = result;
console.log(data?.length); //=> no greater than 25
1query FindManyUsers($first: Int, $after: String) {
2 users(first: $first, after: $after) {
3 edges {
4 cursor
5 node {
6 __typename
7 id
8 # ...
9 createdAt
10 email
11 updatedAt
12 }
13 }
14 pageInfo {
15 endCursor
16 hasNextPage
17 hasPreviousPage
18 startCursor
19 }
20 }
21}
Variables
json
{ "first": 25 }

The after cursor used in this example data won't return any records if used in a real API request.

Next 25 User records after cursor
const userRecords = await api.user.findMany({ after: "abcdefg", first: 25 });
const [result, refresh] = useFindMany(api.user, { after: "abcdefg", first: 25 });
const { data, error, fetching } = result;
1query FindManyUsers($first: Int, $after: String) {
2 users(first: $first, after: $after) {
3 edges {
4 cursor
5 node {
6 __typename
7 id
8 # ...
9 createdAt
10 email
11 updatedAt
12 }
13 }
14 pageInfo {
15 endCursor
16 hasNextPage
17 hasPreviousPage
18 startCursor
19 }
20 }
21}
Variables
json
{ "first": 25, "after": "abcdefg" }

Pagination Limits

Root level record finders like users support a maximum page size of 250 records, and a default page size of 50 records. The page size is controlled using the first or last GraphQL field arguments.

Related record finders that access lists of records through a HasMany or HasManyThrough field support a maximum page size of 100 records, and a default page size of 50 records.

Get the next or previous page

When using the generated JavaScript API client, the record lists returned from find many calls can be paginated using the nextPage() or previousPage() option.

Both nextPage() and previousPage() will throw an error if the corresponding hasNextPage or hasPreviousPage is false.

JavaScript
1const userRecords = await api.user.findMany();
2if (userRecords.hasNextPage) {
3 const nextPage = await userRecords.nextPage();
4}
5if (userRecords.hasPreviousPage) {
6 const prevPage = await userRecords.previousPage();
7}

Selecting fields, and fields of fields

When using the JavaScript client, all of findOne, maybeFindOne, findMany, findFirst, maybeFindFirst, and various action functions, allow requesting specific fields of a User and its relationships. The select option controls which fields are selected in the generated GraphQL query sent to the Gadget API. Pass each field you want to select in an object, with true as the value for scalar fields, and a nested object of the same shape for nested fields.

Gadget has a default selection that will retrieve all of the scalar fields for a User. If you don't pass a select option to a record finder, this default selection will be used.

Select only some User fields
1// fetch only the id, state, and createdAt field
2const userRecords = await api.user.findMany({
3 select: { id: true, state: true, createdAt: true },
4});
5// fetch all the scalar fields for the model, but no relationship fields
6const userRecords = await api.user.findMany();
1// fetch only the id, state, and createdAt field
2const [result, refresh] = useFindMany(api.user, {
3 select: { id: true, state: true, createdAt: true },
4});
5const { data, error, fetching } = result;
6// fetch all the scalar fields for the model, but no relationship fields
7const [result, refresh] = useFindMany(api.user);
8const { data, error, fetching } = result;
Type Safety

The select option is fully type safe if you're using TypeScript. The returned GadgetRecord type will have a <Shape> exactly matching the fields and nested fields you selected. For more information, see Type Safety .

This behavior of selecting only some fields is built right into GraphQL. If you want to limit or expand what you retrieve from a GraphQL query, include or exclude those fields in your GraphQL query. For more information on executing GraphQL queries, see GraphQL.

Select nested User fields
1// fetch the id, state, and createdAt field, and fetch some nested fields from an example relationship field named `someRelatedObject`
2const userRecords = await api.user.findMany({
3 select: {
4 id: true,
5 state: true,
6 createdAt: true,
7 someRelatedObject: { id: true, createdAt: true },
8 },
9});
1// fetch the id, state, and createdAt field, and fetch some nested fields from an example relationship field named `someRelatedObject`
2const [result, refresh] = useFindMany(api.user, {
3 select: {
4 id: true,
5 state: true,
6 createdAt: true,
7 someRelatedObject: { id: true, createdAt: true },
8 },
9});
10const { data, error, fetching } = result;

Combining parameters

Sort, search, filtering, selection, and pagination parameters can be combined to access the exact set of records needed for your use case.

Combining Parameters
1const userRecords = await api.user.findMany({
2 search: "<some search query>",
3 sort: { createdAt: "Descending" },
4 filter: { updatedAt: { greaterThan: new Date(Date.now() - 864e5) } },
5 select: { id: true, createdAt: true },
6 first: 25,
7 after: "abcdefg",
8});
1const [result, refresh] = useFindMany(api.user, {
2 search: "<some search query>",
3 sort: { createdAt: "Descending" },
4 filter: { updatedAt: { greaterThan: new Date(Date.now() - 864e5) } },
5 select: { id: true, createdAt: true },
6 first: 25,
7 after: "abcdefg",
8});
9const { data, error, fetching } = result;
1query FindManyUsers(
2 $after: String
3 $before: String
4 $first: Int
5 $last: Int
6 $search: String
7 $sort: [UserSort!]
8 $filter: [UserFilter!]
9) {
10 users(
11 after: $after
12 before: $before
13 first: $first
14 last: $last
15 search: $search
16 sort: $sort
17 filter: $filter
18 ) {
19 edges {
20 cursor
21 node {
22 __typename
23 id
24 createdAt
25 email
26 roles {
27 key
28 name
29 }
30 updatedAt
31 }
32 }
33 pageInfo {
34 endCursor
35 hasNextPage
36 hasPreviousPage
37 startCursor
38 }
39 }
40}
Variables
json
1{
2 "search": "<some search query>",
3 "sort": { "createdAt": "Descending" },
4 "filter": { "updatedAt": { "greaterThan": "2022-11-30T10:43:46.904Z" } },
5 "first": 25,
6 "after": "abcdefg"
7}

Invoking Actions

User records are changed by invoking Actions. Actions are the things that "do" stuff -- update records, make API calls, call backend code, etc. Actions each have one corresponding GraphQL mutation and a corresponding function available in the API client libraries. Nested Actions can also be invoked with the API client, by providing the actions as input to any relationship fields.

Action Result format

Each API action returns results in the same format that includes a success indicator, errors, and the actual result if the action succeeded. The result is the record that was acted on for a model action, or a list of records for a bulk action, or a JSON blob for Global Actions. Model actions that delete the record don't return the record.

The success field returns a boolean indicating if the action executed as expected. Any execution errors are returned in the errors object, which will always be null if success is true or contain ExecutionError objects if success is false.

ExecutionError objects always have a message describing what error prevented the action from succeeding, as well as a code attribute that gives a stable, searchable, human readable error class code for referencing this specific error. Details on each error code can be found in the Errors documentation. All ExecutionError object types returned by the GraphQL object can be one of many types of error, where some types have extra data that is useful for remedying the error. All error types will always have message and code properties, but some, like InvalidRecordError have extra fields for use by clients.

Errors when using the generated client

The generated JavaScript client automatically interprets errors from invoking actions and throws JavaScript Error instances if the action didn't succeed. The Error objects it throws are rich, and expose extra error properties beyond just message and code if they exist.

Errors thrown by the JavaScript client are easiest to catch by using a try/catch statement around an await, like so:

JavaScript
1import {
2 GadgetOperationError,
3 InvalidRecordError,
4} from "@gadget-client/example-app";
5
6// must be in an async function to use `await` syntax
7const runAction = async () => {
8 try {
9 return await api.exampleModel.create({
10 exampleModel: { name: "example record name" },
11 });
12 } catch (error) {
13 if (error instanceof GadgetOperationError) {
14 // a recognized general error has occurred, retry the operation or inspect error.code`
15 console.error(error);
16 } else if (error instanceof InvalidRecordError) {
17 // the submitted input data for the action was invalid, inspect the invalid fields which `InvalidRecordError` exposes
18 console.error(error.validationErrors);
19 } else {
20 // an unrecognized error occurred, like an HTTP connection interrupted error or a syntax error. Re-throw it because it's not clear what to do to fix ti
21 throw error;
22 }
23 }
24};

For more information on error codes, consult the Errors documentation.

User create

Input

create accepts the following input parameters:

create Input Data
1export interface CreateUserInput {
2 email?: (Scalars["String"] | null) | null;
3
4 password?: (Scalars["String"] | null) | null;
5
6 sessions?: (SessionHasManyInput | null)[];
7
8 posts?: (PostHasManyInput | null)[];
9}
10
11export interface CreateUserArguments {
12 user?: CreateUserInput | null;
13}
1input CreateUserInput {
2 email: String
3 password: String
4 sessions: [SessionHasManyInput]
5 posts: [PostHasManyInput]
6}
7
8input CreateUserArguments {
9 user: CreateUserInput
10}
Example create Invocation
1const userRecord = await api.user.create({
2 user: {
3 // field values for User
4 },
5});
6console.log(userRecord.id); //=> a string
1const [result, createUser] = useAction(api.user.create);
2const { data, error, fetching } = result;
3await createUser({
4 user: {
5 // field values for User
6 },
7});
8console.log(data?.id); //=> a string
1mutation ($user: CreateUserInput) {
2 createUser(user: $user) {
3 success
4 errors {
5 message
6 ... on InvalidRecordError {
7 validationErrors {
8 apiIdentifier
9 message
10 }
11 record
12 model {
13 apiIdentifier
14 }
15 }
16 }
17 user {
18 __typename
19 id
20 createdAt
21 email
22 roles {
23 key
24 name
25 }
26 updatedAt
27 }
28 }
29}
Variables
json
{ "user": {} }
Output

create returns the User. In the JS client, the fields returned can be controlled with the select option. In GraphQL, the return format is the action result format, which includes the record if the action was successful. You can include or exclude the fields you need right in the mutation itself.

create Output Data
type CreateUserResult {
success: Boolean!
errors: [ExecutionError!]
user: User
}

User update

Input

update operates on one User in particular, identified by the id variable.update accepts the following input parameters:

update Input Data
1export interface UpdateUserInput {
2 email?: (Scalars["String"] | null) | null;
3
4 password?: (Scalars["String"] | null) | null;
5
6 sessions?: (SessionHasManyInput | null)[];
7
8 posts?: (PostHasManyInput | null)[];
9}
10
11export interface UpdateUserArguments {
12 user?: UpdateUserInput | null;
13}
1input UpdateUserInput {
2 email: String
3 password: String
4 sessions: [SessionHasManyInput]
5 posts: [PostHasManyInput]
6}
7
8input UpdateUserArguments {
9 user: UpdateUserInput
10}
Example update Invocation
1const userRecord = await api.user.update("some-id", {
2 user: {
3 // field values for User
4 },
5});
6console.log(userRecord.id); //=> a string
1const [result, updateUser] = useAction(api.user.update);
2const { data, error, fetching } = result;
3await updateUser({
4 id: "some-id",
5 user: {
6 // field values for User
7 },
8});
9console.log(data?.id); //=> a string
1mutation ($id: GadgetID!, $user: UpdateUserInput) {
2 updateUser(id: $id, user: $user) {
3 success
4 errors {
5 message
6 ... on InvalidRecordError {
7 validationErrors {
8 apiIdentifier
9 message
10 }
11 record
12 model {
13 apiIdentifier
14 }
15 }
16 }
17 user {
18 __typename
19 id
20 createdAt
21 email
22 roles {
23 key
24 name
25 }
26 updatedAt
27 }
28 }
29}
Variables
json
{ "id": "some-id", "user": {} }
Output

update returns the User. In the JS client, the fields returned can be controlled with the select option. In GraphQL, the return format is the action result format, which includes the record if the action was successful. You can include or exclude the fields you need right in the mutation itself.

update Output Data
type UpdateUserResult {
success: Boolean!
errors: [ExecutionError!]
user: User
}

User delete

The delete action destroys the record.

Input

delete operates on one User in particular, identified by the id variable.

Example delete Invocation
await api.user.delete("some-id");
const [result, deleteUser] = useAction(api.user.delete);
const { data, error, fetching } = result;
await deleteUser({
id: "some-id",
});
1mutation ($id: GadgetID!) {
2 deleteUser(id: $id) {
3 success
4 errors {
5 message
6 ... on InvalidRecordError {
7 validationErrors {
8 apiIdentifier
9 message
10 }
11 record
12 model {
13 apiIdentifier
14 }
15 }
16 }
17 }
18}
Variables
json
{ "id": "some-id" }
Output

delete deletes the record, so it returns void in the JS client. In GraphQL it returns only the success and errors from the action result format.

delete Output Data
type DeleteUserResult {
success: Boolean!
errors: [ExecutionError!]
}

User signUp

Input

signUp accepts the following input parameters:

signUp Input Data
1export interface SignUpUserInput {
2 email?: (Scalars["String"] | null) | null;
3
4 password?: (Scalars["String"] | null) | null;
5
6 sessions?: (SessionHasManyInput | null)[];
7
8 posts?: (PostHasManyInput | null)[];
9}
10
11export interface SignUpUserArguments {
12 user?: SignUpUserInput | null;
13}
1input SignUpUserInput {
2 email: String
3 password: String
4 sessions: [SessionHasManyInput]
5 posts: [PostHasManyInput]
6}
7
8input SignUpUserArguments {
9 user: SignUpUserInput
10}
Example signUp Invocation
1const userRecord = await api.user.signUp({
2 user: {
3 // field values for User
4 },
5});
6console.log(userRecord.id); //=> a string
1const [result, signUpUser] = useAction(api.user.signUp);
2const { data, error, fetching } = result;
3await signUpUser({
4 user: {
5 // field values for User
6 },
7});
8console.log(data?.id); //=> a string
1mutation ($user: SignUpUserInput) {
2 signUpUser(user: $user) {
3 success
4 errors {
5 message
6 ... on InvalidRecordError {
7 validationErrors {
8 apiIdentifier
9 message
10 }
11 record
12 model {
13 apiIdentifier
14 }
15 }
16 }
17 user {
18 __typename
19 id
20 createdAt
21 email
22 roles {
23 key
24 name
25 }
26 updatedAt
27 }
28 }
29}
Variables
json
{ "user": {} }
Output

signUp returns the User. In the JS client, the fields returned can be controlled with the select option. In GraphQL, the return format is the action result format, which includes the record if the action was successful. You can include or exclude the fields you need right in the mutation itself.

signUp Output Data
type SignUpUserResult {
success: Boolean!
errors: [ExecutionError!]
user: User
}

Linking to an Existing Child Record

During a create or update operation, you can link to existing child records simply by nesting the data structure on your operation, using an update object wrapper around the child record's properties.

Existing nested child
1const userRecord = await api.user.create({
2 user: {
3 email: "emailValue",
4 sessions: {
5 // Updates existing `session` record
6 // (`id` of record required),
7 // and links it to user.
8 update: {
9 id: "123",
10 user: "sessionsUserValue",
11 },
12 },
13 },
14});
15console.log(userRecord.id); //=> a string
1const [result, createUser] = useAction(api.user.create);
2const { data, error, fetching } = result;
3await createUser({
4 user: {
5 email: "emailValue",
6 sessions: {
7 // Updates existing `session` record
8 // (`id` of record required),
9 // and links it to user.
10 update: {
11 id: "123",
12 user: "sessionsUserValue",
13 },
14 },
15 },
16});
17console.log(data?.id); //=> a string
1mutation ($user: CreateUserInput) {
2 createUser(user: $user) {
3 success
4 errors {
5 message
6 }
7 user {
8 id
9 email
10 sessions {
11 edges {
12 node {
13 id
14 }
15 }
16 }
17 }
18 }
19}
Variables
json
{
"email": "emailValue",
"sessions": { "update": { "id": "123", "user": "sessionsUserValue" } }
}

Linking to a New Child Record

During a create or update operation, you can create linked child records simply by nesting the data structure on your operation, using a create object wrapper around the child record's properties.

New nested child
1const userRecord = await api.user.create({
2 user: {
3 email: "emailValue",
4 sessions: {
5 // Creates `session` record,
6 // linked to user.
7 create: {
8 user: "sessionsUserValue",
9 },
10 },
11 },
12});
13console.log(userRecord.id); //=> a string
1const [result, createUser] = useAction(api.user.create);
2const { data, error, fetching } = result;
3await createUser({
4 user: {
5 email: "emailValue",
6 sessions: {
7 // Creates `session` record,
8 // linked to user.
9 create: {
10 user: "sessionsUserValue",
11 },
12 },
13 },
14});
15console.log(data?.id); //=> a string
1mutation ($user: CreateUserInput) {
2 createUser(user: $user) {
3 success
4 errors {
5 message
6 }
7 user {
8 id
9 email
10 sessions {
11 edges {
12 node {
13 id
14 }
15 }
16 }
17 }
18 }
19}
Variables
json
{ "email": "emailValue", "sessions": { "create": { "user": "sessionsUserValue" } } }

Linking to an Existing Parent Record

When you wish to link to an existing parent record, you must use a _link property in your data, with the id of the parent record that this child record will belong to.

Linked creation
1const sessionRecord = await api.session.create({
2 session: {
3 // Links session to existing
4 // parent `user` record.
5 user: {
6 _link: "123",
7 },
8 },
9});
10console.log(sessionRecord.id); //=> a string
1const [result, createSession] = useAction(api.session.create);
2const { data, error, fetching } = result;
3await createSession({
4 session: {
5 // Links session to existing
6 // parent `user` record.
7 user: {
8 _link: "123",
9 },
10 },
11});
12console.log(data?.id); //=> a string
1mutation ($session: CreateSessionInput) {
2 createSession(session: $session) {
3 success
4 errors {
5 message
6 }
7 session {
8 id
9 user
10 user {
11 id
12 }
13 }
14 }
15}
Variables
json
{ "user": { "_link": "123" } }

Linking to a New Parent Record

You cannot directly link to a new parent record when creation a child record. However, you can jointly create both parent and child via the Linking to a New Child Record method.

Bulk Actions

Actions that support it can be performed in bulk. Bulk Actions are executed as a single GraphQL mutation and have a corresponding function available in the API client libraries. Bulk Actions are performed on a set of ids. Bulk Actions repeat the same action, with the same options and parameters, across all ids and should not be confused with batching up different actions in the same request.

Bulk Actions will be performed on the entire set. If an action fails on an individual record, the Bulk Action will still occur on the other records in the set. Only the records which completed the action successfully will be returned.

Bulk User delete

bulkDeleteUsers action destroys the records.

Input

bulkDeleteUsers operates on a set of Users, identified by the ids variable.

Example bulkDeleteUsers Invocation
await api.user.bulkDelete(["some-id", "another-id"]);
const [userResult, bulkDelete] = useBulkAction(api.user.bulkDelete);
const { data, error, fetching } = result;
await bulkDelete({ ids: ["some-id", "another-id"] });
1mutation ($ids: [GadgetID!]!) {
2 bulkDeleteUsers(ids: $ids) {
3 success
4 errors {
5 message
6 }
7 }
8}
Variables
json
{ "ids": ["some-id", "another-id"] }
Output

bulkDeleteUsers deletes the record, so it returns void in the JS client. In GraphQL it returns only the success and errors from the action result format.

bulkDeleteUsers Output Data
type BulkDeleteUsersResult {
success: Boolean!
errors: [ExecutionError!]
}