Skip to content

Conversation

@lg2de
Copy link
Contributor

@lg2de lg2de commented Aug 17, 2022

Any thoughts before I continue, @dennisdoomen, @jnyrup?

@jnyrup
Copy link
Member

jnyrup commented Aug 28, 2022

Sorry for the silence.
I would prefer to discuss new APIs in issues before heading to implementations as it makes it easier for us to only focus on the shape of the API and not the implementation details.
Please open an issue and if possible provide some thoughts/examples about the use cases.

This reminds me that I have to finish some documentation on the procress of proposing new APIs.
It will be heavily inspired by https://github.com/dotnet/runtime/blob/main/docs/project/api-review-process.md, but scaled down to a two-person OSS project.

@coveralls
Copy link

coveralls commented Dec 5, 2022

Pull Request Test Coverage Report for Build 3623512252

Details

  • 31 of 33 (93.94%) changed or added relevant lines in 1 file are covered.
  • 18 unchanged lines in 2 files lost coverage.
  • Overall coverage increased (+0.2%) to 96.847%

Changes Missing Coverage Covered Lines Changed/Added Lines %
Src/FluentAssertions/Specialized/AsyncFunctionAssertions.cs 31 33 93.94%
Files with Coverage Reduction New Missed Lines %
Src/FluentAssertions/Specialized/AsyncFunctionAssertions.cs 7 92.4%
Src/FluentAssertions/Data/DataEquivalencyAssertionOptions.cs 11 86.73%
Totals Coverage Status
Change from base Build 3363358641: 0.2%
Covered Lines: 12462
Relevant Lines: 12713

💛 - Coveralls

@jnyrup jnyrup changed the title Added ThrowsWithinAsync assertions Added ThrowWithinAsync assertions Dec 5, 2022
@lg2de lg2de force-pushed the throw-within branch 2 times, most recently from 3f6c983 to b7d37ef Compare December 7, 2022 18:45
@lg2de
Copy link
Contributor Author

lg2de commented Dec 7, 2022

Fixes #2034

@lg2de lg2de marked this pull request as ready for review December 7, 2022 19:00
@jnyrup jnyrup added the feature label Dec 29, 2022
@dennisdoomen
Copy link
Member

Now that the API is approved, I guess you can continue, right?

@lg2de
Copy link
Contributor Author

lg2de commented Jan 6, 2023

Now that the API is approved, I guess you can continue, right?

Yes, so far I did not have sufficient time.

@lg2de lg2de marked this pull request as draft January 14, 2023 17:33
@lg2de lg2de force-pushed the throw-within branch 2 times, most recently from b3c3867 to 69ee4f5 Compare January 14, 2023 17:51
@lg2de lg2de marked this pull request as ready for review January 14, 2023 17:52
Copy link
Member

@jnyrup jnyrup left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks really good, thanks!

Only a few comments about test coverage.

@lg2de lg2de force-pushed the throw-within branch 2 times, most recently from 091fadc to 9f1ff30 Compare January 15, 2023 15:54
@lg2de lg2de force-pushed the throw-within branch 2 times, most recently from ecad736 to 1e8d762 Compare January 16, 2023 08:25
@lg2de
Copy link
Contributor Author

lg2de commented Jan 21, 2023

Please note that I create my commits always to be merged without squashing.
If you disagree with my commits please drop me a note.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Missing ThrowWithinAsync similar to CompleteWithinAsync

6 participants