-
-
Notifications
You must be signed in to change notification settings - Fork 158
Feat/#211 #220
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feat/#211 #220
Conversation
Alright. I will try to fix those test failures. |
I added some unit tests and also took the liberty of simplifying the paging acceptance tests by reducing the amount of logic in the assert sections. |
.ToListAsync()) | ||
.OrderBy(t => t.Id) | ||
.ToList(); | ||
return await entities.PageForward(pageSize, pageNumber).ToListAsync(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why are you calling the ToListAsync()
extension method over your own this.ToListAsync(/*...*/)
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No particular reason. I thought, the extension methods are an implementation detail anyway. We can use the repo's own method if you like that better.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's fair, I suppose the query realization methods exposed here are really only required for the service layer's use. I'm fine with this.
Closes #211
FEATURE