This repository has been archived by the owner on Sep 3, 2021. It is now read-only.
Nested ordering, temporal / enum ordering, large schemas #188
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
upstream update
Addition of enums and temporal type fields on orderBy input types orderBy fields are now list types
michaeldgraham
changed the title
johnymontana
approved these changes
Feb 6, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains support for nested ordering with the use of
apoc.coll.sortMulti. The use ofsortMultihandles lists oforderByarguments, as introduced in #184. Enums and temporal types have also been added as valid ordering arguments.Fixes
Ordering
#47 (Nested ordering) Specify ordering
#162 Ordering by temporal type
#168 Enum types not added to orderBy
Large Schemas
#172 'Maximum call stack size exceeded' on large schema
Other
The
_idfield is no longer added to a type when it is excluded from the generated Query API.Planned
The
first,offset, andorderByarguments can be added to relation type fields during the augmentation process. After which, we can address #173 for ordering by temporal fields on relation types.