Open Chriscbr opened 8 months ago
I wonder if there's a simpler way to support more matchers since this design would imply some need for expect.arrayContains()
, expect.setContains()
, expect.mapContains()
, etc. so it's worth considering if there are alternative designs.
Use Case
An API that display appropriate error messages in CI when the check fails.
Today if you use:
The program will error, but the error message won't show you either of the strings, making it harder to debug why it failed:
This can be addressed by adding log statements, but a cleaner solution would be to provide a dedicated
expect
API that shows the concrete values in the error message:Proposed Solution
No response
Implementation Notes
No response
Component
SDK
Community Notes