chore(deps): Bump ndc-models from v0.1.6 to v0.2.0

[dependabot]

Bumps ndc-models from v0.1.6 to v0.2.0.

Release notes

Sourced from ndc-models's releases.

v0.2.0

Breaking Changes

• ComparisonTarget::RootCollectionColumn was removed and replaced by named scopes (RFC)
• path was removed from ComparisonTarget::Column (RFC)
• AggregateFunctionDefinition was changed to an enum, to support standardized aggregate functions (RFC)
• ComparisonValue::Column no longer uses ComparisonTarget to pick the column. Instead, the necessary column and pathing details are inlined onto the enum variant.
• Declarations of foreign keys has moved from CollectionInfo to ObjectType. This enables object types nested within a collection's object type to declare foreign keys.
• The target column in column mappings can now reference an object-nested field. The target column is now a field path (Vec<FieldName>) instead of just a field (FieldName). Column mappings occur in:
  • Relationship::column_mapping
  • ForeignKeyConstraint::column_mapping
• Scalar type representations are now required, and the previously deprecated number and integer representations have been removed.
• If the capability query.aggregates is enabled, it is now expected that the new schema property capabilities.query.aggregates is also returned.

Specification

Grouping

A new section was added to the specification which allows callers to group rows and aggregate within groups, generalizing SQL's GROUP BY functionality.

Extraction Functions

Extraction functions were added to the schema response to facilitate grouping by components of complex dimensions.

Named scopes

Root column references were generalized to named scopes. Scopes are introduced by EXISTS expressions, and named scopes allow references to columns outside of the current scope; that is, outside the EXISTS expression. Unlike root column references, named scopes allow the caller to refer to columns in any collection in scope, and not just the root collection.

Nested collections

• NestedField::Collection was added to support querying nested collections.
• Exists predicates can now search nested collections.

Filtering involving nested scalar arrays

Nested scalar arrays can now be compared against in filter expressions.

• Exists predicates can now search nested scalar collections
• Expressions now have nested array comparison operators that can be used to test if a scalar array is empty or if it contains an element

Filter by aggregates

ComparisonTarget was extended to allow filtering by aggregates.

Nested relationships

Nested relationships are relationships where the columns being joined upon exist on nested objects within collection's object type. While NDC 0.1.x supports selecting fields across a relationship that starts from within a nested object, it does not support nested relationships in other contexts, such as filtering and ordering. To resolve this, the following additions have been made:

• ExistsInCollection::Related has gained a field_path field that enables descent through nested fields before applying the relationship. This enables support for filtering across a nested relationship.

... (truncated)

Commits

• e25213f Typo fixes
• b791ebc Add nested relationship filtering/ordering capabilities
• 7d9a094 Clarify where the relation_comparisons capability is used (#204)
• 0926e1a Clarify how filtering and pagination is applied with respect to aggregates an...
• 9c202b9 RFC: Add extraction functions for groupings (#201)
• 66c39d9 Fix missing FieldName type for group aggregates (#200)
• 9ce5e92 Use proper newtype for count_scalar_type and add clarifications to the docume...
• 2fad1c6 Add missing capability (#198)
• f923562 [PQL-63] Add new string comparison operators (#197)
• 12b5aa3 Move the aggregate schema capability and better document it (#195)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.