Open hiaux0 opened 2 years ago
@hiaux0
Please describe in this structure:
STEPS: 1. 2. ...
RESULT: ... EXPECTED: ...
Fixed by 723.
Underlying issue was the same.
Test prob was on a broken deal. Because underlying issue (same clauseIds) was fixed can be moved to Code Complete. But before moving to QA should clean up the existing broken deals on staging.
@dkent600
Able to reproduce this here: https://prime-deals-staging.vercel.app/deal/kHofvxovzrrKmqi5VZeN7A
Steps to reproduce:
How this came up, mentioned here: https://github.com/PrimeDAO/prime-deals-dapp/issues/699#issuecomment-1103611163
STEPS:
RESULT: No comment text
EXPECTED: Has comment text
Investigating a bit:
That comment in question has
isPrivate: "false"
, whereas the other have set it to"true"
.key
decryption field inclauseDiscussions
^ Continuing on the last sentence: But for this case, there are already other comments, that decrypt just fine