Repository navigation
Document NUnit Result inference limitation and typed assertion solution - #313
Draft
sergey-tihon with Copilot wants to merge 2 commits into
Draft
sergey-tihon with Copilot wants to merge 2 commits into
sergey-tihon with Copilot wants to merge 2 commits into
Conversation
…ertions Co-authored-by: sergey-tihon <1197905+sergey-tihon@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix non-provided generics inference in NUnit tests
Document NUnit Result inference limitation and typed assertion solution
Oct 9, 2026
This branch has not been deployed
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.
should equalaccepts the actual value asobj, leaving unusedResulttype parameters unconstrained. Identically printed values can therefore compare unequal asResult<CommitMessage, obj>andResult<CommitMessage, string>.FsUnitTyped.shouldEqual, which links expected and actual types, and the explicit-annotation alternative. Preserve the existing DSL; requiring matching types would break assertions such asshould contain.Ok/Errortype parameters and rejection of unequal payloads or cases.Production behavior remains unchanged.
objmaking test fails #274