-
Notifications
You must be signed in to change notification settings - Fork 255
Remove paginate #195
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
Remove paginate #195
Conversation
…esPaginatedSpec in test Fixture/Specs
Hey @MarkusGnigler, Thank you for your help. In the issue, I also mentioned the |
Specification/src/Ardalis.Specification/Exceptions/DuplicateSkipException.cs
Outdated
Show resolved
Hide resolved
Specification/src/Ardalis.Specification/Exceptions/DuplicateTakeException.cs
Outdated
Show resolved
Hide resolved
Hy @fiseni, oh sure, it's a better exception message. Thanks for your guidance. I also remove the |
Messages were changed from: Duplicate use of the Skip(). Ensure you don't use Skip() in the same specification! To: Duplicate use of Skip(). Ensure you don't use Skip() more than once in the same specification!
Should I also refactor the skip and take builder tests to use more the FluentAssertion library, or is using classic assertions the preferred approach since it's shorter? Tests are located in:
[Fact]
public void ThrowsDuplicateSkipException_GivenSkipUsedMoreThanOnce()
{
Assert.Throws<DuplicateSkipException>(() => new StoreDuplicateSkipSpec());
} [Fact]
public void ThrowsDuplicateSkipException_GivenSkipUsedMoreThanOnce()
{
Action sutAction = () => new StoreDuplicateSkipSpec();
sutAction.Should()
.Throw<DuplicateSkipException>();
} |
I don't mind really. Since we're using fluent assertions in all other places, you can refactor it if you want, so we're consistent. |
The consistent aspect was my first intention. Should i scan other places as well? By me it's already evening, I'll try to commit in the next few days. Wish you a happy new year |
No worries, take your time. Yes, you can refactor other places too. Thank you for the help, it's appreciated. Happy New Year! |
Hey @MarkusGnigler. You requested a review but I don't see any new commits. Do you want me to merge it as it is, or do you want to work on the tests? |
Hi @fiseni. Sry, i think the requested review was a mistake. I don't know, should i create a new PR for the test refactoring or should i stick to the existing one? |
Hi @fiseni I've decided to commit the test assertions to this pr as well, since it's not that big impact. I hope it's ok for you? |
Thanks for the help! |
Thank you as well for your friendly communication and guidance! |
I removed the obsolete Paginate method from issue Remove obsolete Paginate builder action..
Hope this change was sufficient.