Open WhyThat opened 3 years ago
Any thoughts on this solution ?
Sorry for the long delay - I think we were waiting to see how this panned out with bs-bastet, but I've sort of lost track of that too. I think the solution might be to just get rid of bisect_ppx completely - it seems to be having some other issues at this point. One option would be to go back to just using jest --coverage
, which is not ideal, but also not the end of the world. Open to feedback on that.
Hey, This is an attempt to fix #267 by removing
bisect_ppx
from the published package outputs areand