-
Notifications
You must be signed in to change notification settings - Fork 162
Remove aggregation fields for non-List relationships #3013
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
Remove aggregation fields for non-List relationships #3013
Conversation
🦋 Changeset detectedLatest commit: 47acc57 The changes in this PR will be included in the next version bump. This PR includes changesets to release 8 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Performance ReportNo Performance Changes Show Full Table
Old Schema Generation: 43.676s |
Liam-Doodson
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! That tck test is weird but the logic hasn't changed luckily. I guess the order cypher builder has assigned the variables changed for some reason!
|
The failing TCK tests seem to have the new rel type escaping. I assume that's come frome dev but might be worth looking into because did we not say that was going to be a breaking change? |
MacondoExpress
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes look good to me but, to be fair, I'm very confused why the two predicates are translated in a different order in the TCK test!
Btw the cypher-builder variables are different because the query is composed in a different order.
…de/graphql into fix/single-field-aggregations
Well this is merging into |
Ah yes ignore me! |
Description
Aggregation fields were being created for relationship fields to single nodes, which serves no functional utility. These will be removed in 4.0.0.
Note: I have no idea why one of the TCK tests changed here!
Complexity
Complexity: Low
Issue
Closes #2969
Checklist
The following requirements should have been met (depending on the changes in the branch):