Bug 169: Fix exception with pageNumber greater than 1 #172
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
added 3 commits
November 28, 2019 11:41
Add test methods in a new unit test project for X.PagedList.EF to demonstrate the "ArgumentException" described in issue dncuug#169.
Declare a variable 'itemsToSkip' that is calculated upfront and use that variable instead of the calculation in the Skip method. The argument passed to the Skip method then is a DbParameterReferenceExpression so the exception does not occur anymore.
|
Thank you! |
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.
Declare a variable 'itemsToSkip' that is calculated upfront and use that variable instead of the calculation in the Skip method.
The argument passed to the Skip method then is a DbParameterReferenceExpression so the exception does not occur anymore.