Extended API Endpoints #602
Merged
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
Cannot use compiled queries entirely for this yet. Maybe if we upgrade to EF Core 5... sorting would have to be done by referencing properties (like User.Name) with EF.Property<string>(User, "Name") BUT then the order is off due to not handling case sensitivity correctly which can potentially be resolved by specifying collations which isn't supported until EF Core 5.
…layers list so you don't get inventory and other heavy data.
EF hashes and caches queries automatically anyways.
lodicolo
approved these changes
Apr 17, 2021
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.
Users List
Players List
User Name Changes
Player Name Changes
Deleting Users
Deleting Players
Bug Fixes