When testing, do we just expect to see JS output during debugging?

1

Lets say I want to use Jest for my JS testing, and use ReScript binding for Jest. As far as I understand it, I will be testing the actual JS file, not the ReScript file. This means, that when I debug the test and see errors printed out by Jest, it will be JS file and not ReScript file right? Is this a common workflow, or is there a better way?

1 Like
2

Yes, it’s a common workflow

3

I am expecting that with the “uncurried by default” feature in the next compiler the generated JavaScript will be simpler and easier to debug.

3 Likes
4

I see, that makes sense!