nest is_null and logical operator configuration in OpenDD expressions RFC (#562)

Tiny change to the RFC to allow for _is_null / _and / _or / _not field
renaming per-type in the future.

V3_GIT_ORIGIN_REV_ID: e090b300f804d72fe2127a5d769e12b89af44f7b
This commit is contained in:
Abhinav Gupta 2024-05-08 08:04:05 -07:00 committed by hasura-bot
parent f6ebaf345a
commit 5d1f9938e2

View File

@ -102,7 +102,9 @@ definition:
operatorMapping:
_within: int_within
# whether to enable _is_null
enableIsNull: true
isNull:
# This is nested to allow for renaming of is_null here in the future
enable: true
graphql:
typeName: Int_comparison_exp_with_eq_within_and_is_null
```
@ -132,9 +134,13 @@ definition:
# This is optional for relationships to models, and defaults to the filterExpressionType of the model
booleanExpressionType: Artist_bool_exp
# whether to enable _and / _or / _not
enableLogicalOperators: true
logicalOperators:
# This is nested to allow for renaming of logical operators here in the future
enable: true
# whether to enable _is_null
enableIsNull: true
isNull:
# This is nested to allow for renaming of is_null here in the future
enable: true
graphql:
typeName: App_Album_bool_exp
```