Split Type assertions in separate files#1576
Merged
dennisdoomen merged 1 commit intofluentassertions:developfrom May 30, 2021
eNeRGy164:split-type-specs
Merged
Split Type assertions in separate files#1576dennisdoomen merged 1 commit intofluentassertions:developfrom eNeRGy164:split-type-specs
dennisdoomen merged 1 commit intofluentassertions:developfrom
eNeRGy164:split-type-specs
Conversation
Member
Contributor
Author
|
I can change it of course. When organizing, I was thinking how logical it is for anybody looking at the code independent of IDE features that both the positive and negative version are in the same file. I was imagining several ways (that are allowed by the filesystem). So, the file containing: |
Member
|
Yes, I understand, but I don't quite like it myself. |
Member
|
I would prefer if we just left out the |
Contributor
Author
jnyrup
approved these changes
May 29, 2021
dennisdoomen
approved these changes
May 30, 2021
This file contains hidden or 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
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.

As discussed in #1551
<content>instead of<summary>to make sure StyleCop rules were passing, but any documentation (unlikely) would come from a single source.NotHavePropertyOfTspecs are missingIMPORTANT