Issue #349: Per-request query options are not preserved with the new $batch execution - #574
Merged
Conversation
…$batch execution Customer may retrieve the query from main request ($batch) that will create IQueryFeature into the Main HttpContext, Once created, it will cached in the main HttpContext. We should remove IQueryFeature and don't pass that to the sub request. Otherwise, the sub request query string will never be used.
Member
Author
garegina
approved these changes
Apr 22, 2022
Merged
1 task
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.
#349
Customers may retrieve the query from the main request ($batch) that will create IQueryFeature into the Main HttpContext, Once created, it will cache in the main HttpContext. We should remove IQueryFeature and don't pass that to the subrequest. Otherwise, the sub-request query string will never be used.