currentUser to check authorizations to update/create some fields
Disable the form
Passing directly a document (TODO: not yet tested in the new version)
Document id in update mode
Callback ran on first render
A GraphQL fragment used to specify the data to return once a mutation is complete.
If no fragment is passed, SmartForm will only return fields used in the form, but note that this might sometimes lead to discrepancies when compared with documents already loaded on the client.
An example would be a createdAt date added automatically on creation even though it’s not part of the actual form. If you’d like that field to be returned after the mutation, you can define a custom mutationFragment that includes it explicitly.
Can be either a string or a DocumentNode (using "gql" tag)
Force a mutation fragment name
NOTE: needed only for string fragments If you use a DocumentNode (with "gql" tag), it will be computed automatically
A GraphQL fragment used to specify the data to fetch to populate edit forms. If no fragment is passed, SmartForm will do its best to figure out what data to load based on the fields included in the form.
Can be either a string or a DocumentNode (using "gql" tag)
Force a query fragment name
NOTE: needed only for string fragments If you use a DocumentNode (with "gql" tag), it will be computed automatically
Passing directly a raw schema (TODO: model is still mandatory atm)
Will prevent leaving the page/unmounting the form on unsaved changes
The result is usually extracted from a graphql mutation But we have a simplified abstracted API, so we could also use the Form without graphql
Function that retriggers data fetching in edit mode Usually provided by the useSingle but could be any function
Generated using TypeDoc
Label so that graphql queries are contextualized