Conversation
This was referenced Feb 6, 2026
Merged
Member
Author
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #424 +/- ##
==========================================
Coverage 100.00% 100.00%
==========================================
Files 108 108
Lines 14785 14869 +84
Branches 1288 745 -543
==========================================
+ Hits 14785 14869 +84
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
844397b to
c475a0e
Compare
674d0b3 to
b8ff387
Compare
c475a0e to
9de79ed
Compare
b8ff387 to
273d1df
Compare
9de79ed to
bacc551
Compare
bacc551 to
8bc9c11
Compare
8bc9c11 to
2b671cb
Compare
This was referenced Feb 10, 2026
quinlanj
approved these changes
Feb 12, 2026
Member
Author
Merge activity
|
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.

Why
Noticed while creating an upcoming pagination PR that loaders should use
TSelectedFieldsfororderByclauses. This was an accidental omission when the selected fields concept was added.Succinctly, one should only be able to order entities by their fields rather than by all their underlying table's fields.
How
Create new orderBy clause type that lives at the loader level. It is fully compatible (subset or equal to) the database orderBy clause, so calling the data manager methods directly with the arguments is by design.
Test Plan
yarn tsc