Skip to content

Add aggregate to migration guide deprecations #246

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

Closed
wants to merge 3 commits into from
Closed
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
41 changes: 41 additions & 0 deletions modules/ROOT/pages/migration/index.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -564,3 +564,44 @@ A warning is raised if you use a deprecated value.
=== Deprecated aggregations on ID fields

Aggregations on ID fields are now deprecated and will be removed in the future.


=== Deprecated aggregation operations

Explicit aggregation operations, both top-level and nested, have been deprecated in favor of the `aggregate` field inside connection operations.

For example:

[source, graphql, indent=0]
----
query {
moviesAggregate {
count
title {
shortest
}
}
}
----

The previous query is deprecated in favor of the following:

[source, graphql, indent=0]
----
query {
moviesConnection {
aggregate {
node {
title {
shortest
}
}
count {
nodes
}
}
}
}
----

Note that `count` now returns the explicit fields `nodes` and `edges`.