I think a good way to solve this would be to extend expect and write the matchers in ReScript code, then have consumers of the library install that in their test setup. It would also allow better support for ReScript-native types like List, Option, and Result, like customizing the error messages you see.
When writing tests in this branch
I get the following result for this code:
I think a good way to solve this would be to extend expect and write the matchers in ReScript code, then have consumers of the library install that in their test setup. It would also allow better support for ReScript-native types like List, Option, and Result, like customizing the error messages you see.