Skip to content

Conversation

@IT-VBFK
Copy link
Contributor

@IT-VBFK IT-VBFK commented Nov 28, 2022

Authored by @siewers, committed by @IT-VBFK

Closes #2045

IMPORTANT

  • The code complies with the Coding Guidelines for C#.
  • The changes are covered by unit tests which follow the Arrange-Act-Assert syntax and the naming conventions such as is used in these tests.
  • If the PR adds a feature or fixes a bug, please update the release notes with a functional description that explains what the change means to consumers of this library, which are published on the website.
  • If the PR changes the public API the changes needs to be included by running AcceptApiChanges.ps1 or AcceptApiChanges.sh.
  • If the PR affects the documentation, please include your changes in this pull request so the documentation will appear on the website.

@dennisdoomen
Copy link
Member

Is this still work in progress?

@IT-VBFK IT-VBFK force-pushed the issue-2045 branch 2 times, most recently from 784056a to 0c77b25 Compare November 28, 2022 19:38
@IT-VBFK
Copy link
Contributor Author

IT-VBFK commented Nov 28, 2022

Not really, why?

@dennisdoomen
Copy link
Member

Just checking whether I can start reviewing it.

@IT-VBFK
Copy link
Contributor Author

IT-VBFK commented Nov 28, 2022

Oh.. yes :)
sorry

@coveralls
Copy link

coveralls commented Nov 28, 2022

Pull Request Test Coverage Report for Build 3794573532

Details

  • 3 of 3 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.9%) to 96.94%

Totals Coverage Status
Change from base Build 3789210470: 0.9%
Covered Lines: 12476
Relevant Lines: 12719

💛 - Coveralls

@jnyrup
Copy link
Member

jnyrup commented Nov 28, 2022

Please, can we agree on the API in #2045 first. 🙏

I see I really need to get this written, but the label "api-suggestion" is supposed to mean "this is a suggestion for a modification to the public api, but it is not yeat ready for implementation".
"api-approved" is "this is ready for implementation".

@IT-VBFK
Copy link
Contributor Author

IT-VBFK commented Nov 28, 2022

Please, can we agree on the API in #2045 first. 🙏

Then.. I will make this a WIP..

@IT-VBFK IT-VBFK marked this pull request as draft November 28, 2022 19:46
@IT-VBFK IT-VBFK force-pushed the issue-2045 branch 2 times, most recently from 7a51917 to 95e4eff Compare December 28, 2022 14:22
@IT-VBFK IT-VBFK marked this pull request as ready for review December 28, 2022 15:30
@jnyrup jnyrup added the feature label Dec 29, 2022
@jnyrup jnyrup requested a review from dennisdoomen December 30, 2022 11:09
@IT-VBFK
Copy link
Contributor Author

IT-VBFK commented Dec 30, 2022

Just a note: Please make sure to add the line "Authored by @siewers, committed by @IT-VBFK" in the commit message, to give @siewers the credit for the change, because it is actually his work :)

@IT-VBFK IT-VBFK changed the title Add extensions for occurrence constraint that reads more fluently Add extensions for OccurrenceConstraint that reads more fluently Dec 30, 2022
Copy link
Member

@dennisdoomen dennisdoomen left a comment

Choose a reason for hiding this comment

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

Please also update strings.md to show the new way.

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.

Include extension methods for OccurrenceConstraint that reads more fluently

4 participants