clarify computed field fns need not be tracked

PR-URL: https://github.com/hasura/graphql-engine-mono/pull/6151
Co-authored-by: Sean Park-Ross <94021366+seanparkross@users.noreply.github.com>
GitOrigin-RevId: e5afbf12bdf2ed7439e535e168152e876a6260cb
This commit is contained in:
Rikin Kachhia 2022-12-22 16:20:23 +05:30 committed by hasura-bot
parent a8a36bf7ee
commit 73e333a412
2 changed files with 6 additions and 11 deletions

View File

@ -378,7 +378,8 @@ const RawSQL = ({
</label>
<Tooltip
message={
'If you are creating tables, views or functions, checking this will also expose them over the GraphQL API as top level fields'
'If you are creating tables, views or functions, checking this will also expose them over the GraphQL API as ' +
'top level fields. Functions only intended to be used as computed fields should not be tracked.'
}
/>
&nbsp;

View File

@ -43,8 +43,9 @@ from_ [Postgres docs](https://www.postgresql.org/docs/current/sql-createfunction
:::info Note
Functions used as computed fields can also accept other arguments other than the mandatory table row argument. Values
for these extra arguments can be passed as arguments to the computed field in the GraphQL API.
- Functions used as computed fields can also accept other arguments other than the mandatory table row argument. Values
for these extra arguments can be passed as arguments to the computed field in the GraphQL API.
- Functions used as computed fields do not need to be tracked by the Hasura GraphQL Engine.
:::
@ -182,14 +183,7 @@ Query data from the `authors` table:
Head to the `Modify` tab of the table/view and click on the `Add` button in the `Computed fields` section:
<Thumbnail src="/img/schema/computed-field-create.png" alt="Add computed field" />
:::tip Supported from
- Console support for tables is available in `v1.1.0` and above
- Console support for views is available in `v1.3.0` and above
:::
<Thumbnail src='/img/schema/computed-field-create.png' alt='Add computed field' width='750px' />
</TabItem>
<TabItem value="cli" label="CLI">