Fix connection ordering check when Include() strips IOrderedQueryable…#1262
Merged
SimonCropp merged 1 commit intoSimonCropp:mainfrom Mar 26, 2026
Merged
Conversation
… for entities with read-only properties
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
2 participants
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.
Hey Simon
Connection queries break with "Connections require ordering" when the entity has read-only properties. Projection bails on read-only props, falls back to AddIncludes, and .Include() strips IOrderedQueryable even though the ordering is still in the expression tree.
Fix:
When the is IOrderedQueryable check fails, walk the expression tree for OrderBy/OrderByDescending.
I've add some Tests and add ReadOnlyEntity test data to reproduce it.