docs: add FAQ on how to sort by DTO fields or aliases #933
Conversation
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
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.
Motivation
The documentation did not explicitly cover how to sort query results by a computed or aggregated field in a DTO projection. This PR adds a new FAQ page to demonstrate how to use aliases in the
selectclause and refer to them in theorderByclause.Modifications
docs/en/faq/how-to-sort-by-dto-fields-or-aliases.mddocs/ko/faq/how-to-sort-by-dto-fields-or-aliases.mddocs/en/SUMMARY.mdanddocs/ko/SUMMARY.mdto include the new FAQ.Result
After this PR is merged, users will have a clear example of how to sort by aliased fields, making it easier to handle complex ordering requirements in their queries.