Feat: support nested relation subqueries with sorting, pagination, and projection (the too much lines changes are caused from the generated client not me) - #37
Merged
Conversation
VoidClancy
changed the title
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
1- Define OrderDirection (Asc, Desc) and OrderBy structs in runtime, registering them under QueryParams
2- Implement Asc() and Desc() methods on Field[T], UniqueField[T], StringField, and StringUniqueField to return OrderBy structs
3- Introduce model-specific SelectQuery interfaces exposing GetRelationParams() returning (Select, Omit, QueryParams)
4- Implement GetRelationParams() on both raw Select structs and QueryBuilders, allowing mixing of simple nested struct projection and subqueries
5- Remove redundant relationship fields from generated Omit structs, since relationships are never fetched unless explicitly requested
6- Refactor loadRelation[P any, C any] into modular, separate responsibility functions (compileRelationSQL, compilePartitionedRelationSQL, and compileSimpleRelationSQL helpers)
7- Add TestRelationSubqueries test suite to test complex subqueries