WIP: server/aspnetcore: Add initial UCAST->LINQ plumbing. #425
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
philipaconrad
added
enhancement
This commit provides a first stab at UCAST LINQ support, via the IQueryable<T> interface. Signed-off-by: Philip Conrad <[email protected]>
philipaconrad
force-pushed
the
philip/ucast-aspnetcore-server
branch
from
c708397
to
ea11b1b
Compare
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.
What changed?
This PR is a first stab at UCAST -> LINQ support, via the
IQueryable<T>interface. There's a lot of TODOs, mostly around making sure the LINQ reflection stuff is working as-intended. Not everything works just yet!Tables JOINs are also a big unknown, which I plan to at least look into, and maybe support with document-level ops (
includeorjoinwould be good examples that hew close to existing LINQ stuff).References