Post

This page documents the Post model.

Data Shape

Gadget's database stores Post 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 Post:

1export interface Post {
2  __typename: "Post";
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  title: Scalars["String"] | null;
14
15  body: RichText | null;
16
17  published: Scalars["String"] | null;
18
19  author: User | null;
20
21  authorId: Scalars["GadgetID"] | null;
22
23  /** Get all the fields for this record. Useful for not having to list out all the fields you want to retrieve, but slower. */
24  _all: Scalars["JSONObject"];
25}

1type Post {
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  title: String
17  body: RichText
18  published: String
19  author: User
20  authorId: GadgetID
21
22  """
23  Get all the fields for this record. Useful for not having to list out all the fields you want to retrieve, but slower.
24  """
25  _all: JSONObject!
26}

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

Any fetched Post record will have this same Post 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 Post record

Individual Post 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.

const postRecord = await api.post.findOne("some-id");
console.log(postRecord.id); //=> a string
console.log(postRecord.createdAt); //=> a Date object

const [result, refresh] = useFindOne(api.post, "some-id");
const { data, error, fetching } = result;
console.log(data?.id); //=> a string
console.log(data?.createdAt); //=> a Date object

1query GetOnePost($id: GadgetID!) {
2  post(id: $id) {
3    __typename
4    id
5    body {
6      markdown
7      truncatedHTML
8    }
9    createdAt
10    published
11    title
12    updatedAt
13  }
14}

{ "id": "some-id" }

Retrieving the first of many Post 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.

const postRecord = await api.post.findFirst();
console.log(postRecord.id); //=> a string
console.log(postRecord.createdAt); //=> a Date object

const [result, refresh] = useFindFirst(api.post);
const { data, error, fetching } = result;
console.log(data?.id); //=> a string
console.log(data?.createdAt); //=> a Date object

1query FindManyPosts(
2  $first: Int
3  $search: String
4  $sort: [PostSort!]
5  $filter: [PostFilter!]
6) {
7  posts(first: $first, search: $search, sort: $sort, filter: $filter) {
8    edges {
9      node {
10        __typename
11        id
12        body {
13          markdown
14          truncatedHTML
15        }
16        createdAt
17        published
18        title
19        updatedAt
20      }
21    }
22  }
23}

{ "first": 1 }

Retrieving many Post records

Pages of Post 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 posts 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 Posts

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

const postRecords = await api.post.findMany();
console.log(postRecords.length); //=> a number
console.log(postRecords[0].id); //=> a string

const [result, refresh] = useFindMany(api.post);
const { data, error, fetching } = result;
console.log(data?.length); //=> a number
console.log(data?.[0].length); //=> a string

1query FindManyPosts {
2  posts {
3    edges {
4      node {
5        __typename
6        id
7        # ...
8        createdAt
9        title
10        updatedAt
11      }
12    }
13  }
14}

{}

Retrieving a single Post 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 Post record by ID

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

const postRecord = await api.post.findById("some-value");
console.log(postRecord.id); //=> a string

const [result, refresh] = useFindBy(api.post.findById, "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 PostSort 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 PostSort instead of just one.

1input PostSort {
2  id: SortOrder
3  createdAt: SortOrder
4  updatedAt: SortOrder
5  title: SortOrder
6  body: SortOrder
7  published: SortOrder
8}

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

const postRecords = await api.post.findMany({ sort: { createdAt: "Descending" } });

const [result, refresh] = useFindMany(api.post, {
  sort: { createdAt: "Descending" },
});
const { data, error, fetching } = result;

1query FindManyPosts($sort: [PostSort!]) {
2  posts(sort: $sort) {
3    edges {
4      node {
5        __typename
6        id
7        # ...
8        createdAt
9        title
10        updatedAt
11      }
12    }
13  }
14}

{ "sort": { "createdAt": "Descending" } }

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

const postRecords = await api.post.findMany({
  sort: [{ state: "Descending" }, { createdAt: "Ascending" }],
});

const [result, refresh] = useFindMany(api.post, {
  sort: [{ state: "Descending" }, { createdAt: "Ascending" }],
});
const { data, error, fetching } = result;

1query FindManyPosts($sort: [PostSort!]) {
2  posts(sort: $sort) {
3    edges {
4      node {
5        __typename
6        id
7        # ...
8        createdAt
9        title
10        updatedAt
11      }
12    }
13  }
14}

{ "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.

const postRecords = await api.post.findMany({
  sort: { id: "Descending" },
});

const [result, refresh] = useFindMany(api.post, {
  sort: { id: "Descending" },
});
const { data, error, fetching } = result;

1query FindManyPosts($sort: [PostSort!]) {
2  posts(sort: $sort) {
3    edges {
4      node {
5        __typename
6        id
7        # ...
8        createdAt
9        title
10        updatedAt
11      }
12    }
13  }
14}

{ "sort": { "id": "Descending" } }

Searching

Post 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 Posts 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.

const postRecords = await api.post.findMany({
  search: "a specific phrase to search for",
});

const [result, refresh] = useFindMany(api.post, {
  search: "a specific phrase to search for",
});
const { data, error, fetching } = result;

1query FindManyPosts($search: String) {
2  posts(search: $search) {
3    edges {
4      node {
5        __typename
6        id
7        # ...
8        createdAt
9        title
10        updatedAt
11      }
12    }
13  }
14}

{ "search": "a specific phrase to search for" }

Filtering

Post 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 Posts 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 PostFilter 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.

1input PostFilter {
2  AND: [PostFilter]
3  OR: [PostFilter]
4  NOT: [PostFilter]
5  id: IDFilter
6  createdAt: DateTimeFilter
7  updatedAt: DateTimeFilter
8  state: JSONFilter
9  title: StringFilter
10  body: StringFilter
11  published: StringFilter
12  author: IDFilter
13}

const yesterday = new Date(Date.now() - 864e5);
const postRecords = await api.post.findMany({
  filter: { createdAt: { greaterThan: yesterday } },
});

const yesterday = new Date(Date.now() - 864e5);
const [result, refresh] = useFindMany(api.post, {
  filter: { createdAt: { greaterThan: yesterday } },
});
const { data, error, fetching } = result;

1query FindManyPosts($filter: [PostFilter!]) {
2  posts(filter: $filter) {
3    edges {
4      node {
5        __typename
6        id
7        # ...
8        createdAt
9        title
10        updatedAt
11      }
12    }
13  }
14}

{ "filter": { "createdAt": { "greaterThan": "2022-11-30T11:13:34.239Z" } } }

1const yesterday = new Date(Date.now() - 86400000);
2const oneWeekAgo = new Date(Date.now() - 604800000);
3const postRecords = await api.post.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.post, {
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 FindManyPosts($filter: [PostFilter!]) {
2  posts(filter: $filter) {
3    edges {
4      node {
5        __typename
6        id
7        # ...
8        createdAt
9        title
10        updatedAt
11      }
12    }
13  }
14}

1{
2  "filter": {
3    "OR": [
4      { "createdAt": { "greaterThan": "2022-11-24T11:13:34.239Z" } },
5      { "updated": { "greaterThan": "2022-11-30T11:13:34.239Z" } }
6    ]
7  }
8}

Filter records that are in the created state

const postRecords = await api.post.findMany({
  filter: {
    state: { inState: "created" },
  },
});

1const [result, refresh] = useFindMany(api.post, {
2  filter: {
3    state: { inState: "created" },
4  },
5});
6const { data, error, fetching } = result;

1query FindManyPosts($filter: [PostFilter!]) {
2  posts(filter: $filter) {
3    edges {
4      node {
5        __typename
6        id
7        # ...
8        createdAt
9        title
10        updatedAt
11      }
12    }
13  }
14}

{ "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 postRecords = await api.post.findMany({
  filter: {
    id: { isSet: true },
  },
});

1const [result, refresh] = useFindMany(api.post, {
2  filter: {
3    id: { isSet: true },
4  },
5});
6const { data, error, fetching } = result;

1query FindManyPosts($filter: [PostFilter!]) {
2  posts(filter: $filter) {
3    edges {
4      node {
5        __typename
6        id
7        # ...
8        createdAt
9        title
10        updatedAt
11      }
12    }
13  }
14}

{ "filter": { "id": { "isSet": true } } }

Pagination

All Gadget record lists, including the top level Post finder as well as associations to Post, 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 Post 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.

Post 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.

const postRecords = await api.post.findMany({ first: 25 });
console.log(postRecords.length); //=> no greater than 25

const [result, refresh] = useFindMany(api.post, { first: 25 });
const { data, error, fetching } = result;
console.log(data?.length); //=> no greater than 25

1query FindManyPosts($first: Int, $after: String) {
2  posts(first: $first, after: $after) {
3    edges {
4      cursor
5      node {
6        __typename
7        id
8        # ...
9        createdAt
10        title
11        updatedAt
12      }
13    }
14    pageInfo {
15      endCursor
16      hasNextPage
17      hasPreviousPage
18      startCursor
19    }
20  }
21}

{ "first": 25 }

const postRecords = await api.post.findMany({ after: "abcdefg", first: 25 });

const [result, refresh] = useFindMany(api.post, { after: "abcdefg", first: 25 });
const { data, error, fetching } = result;

1query FindManyPosts($first: Int, $after: String) {
2  posts(first: $first, after: $after) {
3    edges {
4      cursor
5      node {
6        __typename
7        id
8        # ...
9        createdAt
10        title
11        updatedAt
12      }
13    }
14    pageInfo {
15      endCursor
16      hasNextPage
17      hasPreviousPage
18      startCursor
19    }
20  }
21}

{ "first": 25, "after": "abcdefg" }

Pagination Limits

Root level record finders like posts 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.

1const postRecords = await api.post.findMany();
2if (postRecords.hasNextPage) {
3  const nextPage = await postRecords.nextPage();
4}
5if (postRecords.hasPreviousPage) {
6  const prevPage = await postRecords.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 Post 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 Post. If you don't pass a select option to a record finder, this default selection will be used.

1// fetch only the id, state, and createdAt field
2const postRecords = await api.post.findMany({
3  select: { id: true, state: true, createdAt: true },
4});
5// fetch all the scalar fields for the model, but no relationship fields
6const postRecords = await api.post.findMany();

1// fetch only the id, state, and createdAt field
2const [result, refresh] = useFindMany(api.post, {
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.post);
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.

1// fetch the id, state, and createdAt field, and fetch some nested fields from an example relationship field named `someRelatedObject`
2const postRecords = await api.post.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.post, {
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.

1const postRecords = await api.post.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.post, {
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 FindManyPosts(
2  $after: String
3  $before: String
4  $first: Int
5  $last: Int
6  $search: String
7  $sort: [PostSort!]
8  $filter: [PostFilter!]
9) {
10  posts(
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        body {
25          markdown
26          truncatedHTML
27        }
28        createdAt
29        published
30        title
31        updatedAt
32      }
33    }
34    pageInfo {
35      endCursor
36      hasNextPage
37      hasPreviousPage
38      startCursor
39    }
40  }
41}

1{
2  "search": "<some search query>",
3  "sort": { "createdAt": "Descending" },
4  "filter": { "updatedAt": { "greaterThan": "2022-11-30T11:13:34.630Z" } },
5  "first": 25,
6  "after": "abcdefg"
7}

Invoking Actions

Post 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:

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.

Post create

Input

create accepts the following input parameters:

1export interface CreatePostInput {
2  title?: (Scalars["String"] | null) | null;
3
4  body?: RichTextInput | null;
5
6  published?: (Scalars["String"] | null) | null;
7
8  author?: UserBelongsToInput | null;
9}
10
11export interface CreatePostArguments {
12  post?: CreatePostInput | null;
13}

1input CreatePostInput {
2  title: String
3  body: RichTextInput
4  published: String
5  author: UserBelongsToInput
6}
7
8input CreatePostArguments {
9  post: CreatePostInput
10}

1const postRecord = await api.post.create({
2  post: {
3    // field values for Post
4  },
5});
6console.log(postRecord.id); //=> a string

1const [result, createPost] = useAction(api.post.create);
2const { data, error, fetching } = result;
3await createPost({
4  post: {
5    // field values for Post
6  },
7});
8console.log(data?.id); //=> a string

1mutation ($post: CreatePostInput) {
2  createPost(post: $post) {
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    post {
18      __typename
19      id
20      body {
21        markdown
22        truncatedHTML
23      }
24      createdAt
25      published
26      title
27      updatedAt
28    }
29  }
30}

{ "post": {} }

Output

create returns the Post. 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.

type CreatePostResult {
  success: Boolean!
  errors: [ExecutionError!]
  post: Post
}

Post update

Input

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

1export interface UpdatePostInput {
2  title?: (Scalars["String"] | null) | null;
3
4  body?: RichTextInput | null;
5
6  published?: (Scalars["String"] | null) | null;
7
8  author?: UserBelongsToInput | null;
9}
10
11export interface UpdatePostArguments {
12  post?: UpdatePostInput | null;
13}

1input UpdatePostInput {
2  title: String
3  body: RichTextInput
4  published: String
5  author: UserBelongsToInput
6}
7
8input UpdatePostArguments {
9  post: UpdatePostInput
10}

1const postRecord = await api.post.update("some-id", {
2  post: {
3    // field values for Post
4  },
5});
6console.log(postRecord.id); //=> a string

1const [result, updatePost] = useAction(api.post.update);
2const { data, error, fetching } = result;
3await updatePost({
4  id: "some-id",
5  post: {
6    // field values for Post
7  },
8});
9console.log(data?.id); //=> a string

1mutation ($id: GadgetID!, $post: UpdatePostInput) {
2  updatePost(id: $id, post: $post) {
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    post {
18      __typename
19      id
20      body {
21        markdown
22        truncatedHTML
23      }
24      createdAt
25      published
26      title
27      updatedAt
28    }
29  }
30}

{ "id": "some-id", "post": {} }

Output

update returns the Post. 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.

type UpdatePostResult {
  success: Boolean!
  errors: [ExecutionError!]
  post: Post
}

Post delete

The delete action destroys the record.

Input

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

await api.post.delete("some-id");

const [result, deletePost] = useAction(api.post.delete);
const { data, error, fetching } = result;
await deletePost({
  id: "some-id",
});

1mutation ($id: GadgetID!) {
2  deletePost(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}

{ "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.

type DeletePostResult {
  success: Boolean!
  errors: [ExecutionError!]
}

Linking Related Records

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.

1const userRecord = await api.user.create({
2  user: {
3    email: "emailValue",
4    posts: {
5      // Updates existing `post` record
6      // (`id` of record required),
7      // and links it to user.
8      update: {
9        id: "123",
10        title: "postsTitleValue",
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    posts: {
7      // Updates existing `post` record
8      // (`id` of record required),
9      // and links it to user.
10      update: {
11        id: "123",
12        title: "postsTitleValue",
13      },
14    },
15  },
16});
17console.log(data?.id); //=> a string