Add @default directive to v22 of dgraph

mahdi78 · February 1, 2023, 9:36am

hi
please add @default directive to v22 from v21.12 .
this merge request in v21.12 added this feature.
thanks.

github.com/dgraph-io/dgraph

feat(graphql): adds @default directive for setting default field values at create and update

dgraph-io:master ← dpeek:graphql-timestamps

opened 07:53AM - 07 Sep 21 UTC

dpeek

+1330 -7

Adds support for `@default` directive to GraphQL input schema. Syntax: ```…graphql type Type { field: FieldType @default( add: {value: "value"} update: { value: "value"} ) } ``` Where a value is not provided as input for a mutation, the `add` value will be used if the node is being created, and the `update` value will be used if the node exists and is being updated. Values are provided as strings, parsed into the correct field type by Dgraph. The string `$now` is replaced by the current DateTime string on the server, ie: ```graphql type Type { createdAt: DateTime! @default( add: { value: "$now" } ) updatedAt: DateTime! @default( add: { value: "$now" } update: { value: "$now" } ) } ``` Schema validation will check that: - `Int` field values can be parsed `strconv.ParseInt` - `Float` field values can be parsed by `strconv.ParseFloat` - `Boolean` field values are `true` or `false` - `$now` can only be used with fields of type `DateTime` (could be extended to include `String`?) Schema validation does not currently ensure that `@default` values for enums are a valid member of the enum, so this is allowed: ```graphql enum State { HOT NOT } type Type { state: State @default(add: { value: "FOO"}) } ``` Schema validation also prevents use of `@default` on: - Types with `@remote` directive - Fields of type `ID` - Fields that are not scalar types (`Int`, `Float`, `String`, `Boolean`, `DateTime`) or an enum - Fields that are list types (ie `[String]) - Fields with `@id`, `@custom`, `@lambda` Output schema changes: - Fields with `@default(add)` values become optional in `AddTypeInput` --- This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/dgraph-io/dgraph/8017)

MichelDiz · February 1, 2023, 4:43pm

Can you check if there is an issue for this? so we can track.

ping @Raphael

Raphael · February 1, 2023, 8:12pm

Yes it is in backlog.

markushedlund · August 2, 2023, 8:00pm

Will this feature come back with the next v23 release?
Looks like it based on the roadmap

Raphael · August 7, 2023, 3:31pm

Should be in one of the v23.x release. The PR is under review…

Topic		Replies	Views
How to use the @default directive? Dgraph Cloud	1	880	May 20, 2022
Directive Default Doesn't work GraphQL dgraph	3	817	October 26, 2022
How to add @id directive Dgraph kind:question , dgraph	1	817	April 3, 2022
Please confirm @default operation Users dgraph	4	798	January 19, 2022
Feature request: Directive that indicates that @id fields should be auto-populated on creation GraphQL	6	646	October 7, 2021

Add @default directive to v22 of dgraph

Related Topics