Request (any Message actually) is not `equals`ed structurally
See original GitHub issueRequest
(and any Message
) are not equal, even if they contain the same elements (empty Vault
, for example)
the reason is that they contain field attributes
of class Vault
, which is not compared structurally
blocked on https://github.com/ChristopherDavenport/vault/pull/51 being merged and new version being published
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
The originally planned final episode for Ed, Edd n Eddy was ...
It revolved around The Ed's, three friends living in Peach Creek Estates, in a state of perpetual summer, with no adult supervision or...
Read more >Relational Equality and the Expressive Dimension of State ...
Answering this question is important, not least because the extent to which we ought to care about this dimension of state action hinges...
Read more >DOM.= RESUME - ERIC
structure that the authoring staffwill utilize to order the author's ... so produce material for the programming staff that requires no. "debugging" of....
Read more >Source code - HAPI FHIR
clearUserData(GENERATED_IN_SNAPSHOT); 712 713 // we actually delegate the work to ... hasId()) { 773 String msg = "No match found in the generated...
Read more >Mount Tai Pilgrimages in Song China, 960-1279 - Brill
political legitimacy and its power structure. ... the expansion of Chinese territory, the sacred peaks no longer marked the fron-.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Request
is no longer a case class.Response
is, but this is misleading. I don’t think equality should be relied upon, and ad hoc definitions of equality for tests should be a test-localEq
instance, like we do forIO
.In fact, I think we should make
Response
not a case class.We used this in tests.