graphql-engine-1.0.0: GraphQL API over Postgres
Safe HaskellSafe-Inferred
LanguageHaskell2010

Hasura.RQL.Types.Schema.Options

Description

Definitions for schema building configuration.

Synopsis

Documentation

data StringifyNumbers Source #

Should we represent numbers in our responses as numbers, or strings? Some backends can return numbers that exceed the bounds of JSON's own number type. In these cases, we can use stringified versions of these numbers to avoid this problem.

data IncludeUpdateManyFields Source #

Should we include TABLE_updates fields in schemas This is a toggle so that users can opt-in, and so that we can rename any tables that this may conflict with if needed

data IncludeStreamFields Source #

Should we include TABLE_stream fields in schemas This is a toggle so that users can opt-in, and so that we can rename any tables that this may conflict with if needed

data IncludeAggregationPredicates Source #

Should we include aggregation functions in where clauses? Because this has the potential to cause naming conflicts in graphql schema types, this flag allows users to toggle the feature off if it an upgrade breaks their setup.

data DangerouslyCollapseBooleans Source #

Should Boolean fields be collapsed to True when a null value is given? This was the behaviour of Hasura V1, and is now discouraged.

data InferFunctionPermissions Source #

Should we infer function permissions? If this flag is set to InferFunctionPermissions, we may fail to build expression parsers in buildQueryAndSubscriptionFields for users with unrecognised roles.

data OptimizePermissionFilters Source #

Should we attempt to deduplicate permission filters? This flag is used in relationshipField to determine whether certain row-level permission filters can be dropped in certain cases.

data UsePostgresArrays Source #

if we use Postgres arrays then an array of text becomes `[String!]`, however we want users to have the option to make it output _text like it did before for compatibility.