Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update compatibility config with new dates #885

Merged
merged 2 commits into from
Feb 7, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
47 changes: 47 additions & 0 deletions docs/reference/metadata-reference/compatibility-config.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,53 @@ will be disabled. To enable these features, simply increase your `date` to a new
The following is a list of dates at which backwards-incompatible changes were added to Hasura DDN. Projects with
CompatibilityConfig `date`s prior to these dates will have these features disabled.

#### 2025-02-08

##### Disallow unsupported orderable relationships

Build errors are now raised if unsupported orderable relationships are defined on OrderByExpressions. Specifically:

- If the relationship is a remote relationship
- If the data connector does not support performing relationships
- If the target Model or Command of the relationship does not have a source defined

##### Disallow relationships where the data connector does not support relationships or remote relationships

A build error is now raised if a Relationship is defined between an ObjectType and a Model or Command that are sourced
from the same data connector, but that data connector does not support performing relationships or support remote
relationships.

#### 2025-02-04

##### Command and argument preset typechecking

A build error is now raised if an argument preset defined in CommandPermissions or ModelPermissions or a field preset in
TypePermissions specifies a literal value that does not match the type of the argument or field it is supposed to be
presetting.

##### Disallow scalar type mismatch in object type fields

A build error is now raised if an ObjectType's field's scalar type does not match the scalar type of the underlying data
connector's object type field. The field's specified scalar type must have a DataConnectorScalarRepresentation defined
that specifies it as the representation for the data connector's scalar type.

##### Disallow unknown ObjectType field types

A build error is now raised if an ObjectType's field's type is an unknown type.

##### Disallow orderable fields that have field arguments

A build error is now raised if an orderable field on an OrderByExpression has field arguments. This scenario is not
supported.

#### 2025-01-25

##### Disallow duplicate scalar type aggregate functions

A build error is now raised if a data connector scalar type has multiple aggregate functions of the same type (for
example, two sum functions for the same scalar type). This ensures that there is no ambiguity when choosing an aggregate
function for a particular purpose (for example, performing a sum aggregate).

#### 2025-01-07

##### Disallow duplicate operator definitions for scalar type
Expand Down
Loading