Commits on Aug 29, 2024

1. Use custom gomega matcher for protobuf equality …

   The standard gomega Equal matcher is not reliable when used with
   protobuf messages since they can be logically equal while containing
   different implementation field values. This change implements a custom
   ProtoEqual matcher that uses proto.Equal for reliable equality checks.
   
   A failed match produces output similar to the following:
   
   ```
   [FAILED] Expected
           ChaincodeMessage{
                   type:  TRANSACTION
                   payload:  "\n\x04arg1\n\x04arg2"
                   txid:  "tx-id"
                   proposal:  {
                           proposal_bytes:  "signed-proposal-bytes"
                           signature:  "signature"
                   }
                   channel_id:  "channel-id"
           }
     to equal
           SignedProposal{
                   proposal_bytes:  "signed-proposal-bytes"
                   signature:  "signature"
           }
   ```
   
   Signed-off-by: Mark S. Lewis <Mark.S.Lewis@outlook.com>

   

   bestbeforetoday committed Aug 29, 2024
   Configuration menu

   • View commit details
   • Copy full SHA for baf360f
   • Browse repository at this point

   Copy the full SHA

   baf360f View commit details

   Browse the repository at this point in the history