feat!: Controlling type formatting in failure reports - #96
Merged
Conversation
…[does not compile yet]
…pes of the representation mechanic
…epresentation" feature
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #96 +/- ##
==========================================
+ Coverage 87.73% 87.84% +0.11%
==========================================
Files 42 42
Lines 6695 7513 +818
Branches 6695 7513 +818
==========================================
+ Hits 5874 6600 +726
- Misses 751 843 +92
Partials 70 70 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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.
The representation feature enables us to define how values of a certain type is represented in the failure report when an assertion fails. The representation can be defined for any type, even for foreign types without breaking the orphan rule. By default the debug representation of a type is used. If a type does not implement
Debugusing a custom representation is mandatory.Breaking Change:
The API for writing custom assertions has changed. It now has an additional parameter 'representation' in many methods. Implementations of the
Expectationtrait should no longer require to implementDebugbut instead depend on theRepresent-trait.Note: This does not break anything when using the crate for writing assertions in tests,