Manually using ODataQueryOptions.Validate and setting SelectExpandQue… #524
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
There was a problem hiding this comment.
Does not see the necessity. Keep consistent with other classes.
|
others looks good to me |
…ryOption.LevelsMaxLiteralExpansionDepth OData#516
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
…ryOption.LevelsMaxLiteralExpansionDepth #516
Although SelectExpandQueryOption.LevelsMaxLiteralExpansionDepth is used to control the actual expansion depth for each request. Although it is for internal use, but it is public so we cannot remove it. In the fix, the value of LevelsMaxLiteralExpansionDepth can be set manually or it will be set automatically to ODataValidationSettings.MaxExpansionDepth.