You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bastet, Relude, and presumably other libraries make use of bisect_ppx during development/CI to collect test coverage stats. In an ideal world, users of those libraries wouldn't also have to depend on bisect_ppx, because it's a dev-only tool that at various points has caused pain when building on Windows, with the Rescript compiler, etc. Currently, I don't believe it's possible to make it a devDependency, because the ppx-flagsfield in our bsconfig will try to run during every build, and it will fail in this case if it doesn't find bisect_ppx.
Maybe a potential solution:
@aantronhad proposed adding a "dev" version of the ppx-flags field to bsconfig.json. This could theoretically allow users of Relude to build a non-development version of the library that skips the bisect_ppx step. There was even a Bucklescript PR that attempted to fix this, but it was never merged.
The problem:
Bastet, Relude, and presumably other libraries make use of
bisect_ppx
during development/CI to collect test coverage stats. In an ideal world, users of those libraries wouldn't also have to depend onbisect_ppx
, because it's a dev-only tool that at various points has caused pain when building on Windows, with the Rescript compiler, etc. Currently, I don't believe it's possible to make it adevDependency
, because theppx-flags
field in our bsconfig will try to run during every build, and it will fail in this case if it doesn't findbisect_ppx
.Maybe a potential solution:
@aantron had proposed adding a "dev" version of the
ppx-flags
field tobsconfig.json
. This could theoretically allow users of Relude to build a non-development version of the library that skips thebisect_ppx
step. There was even a Bucklescript PR that attempted to fix this, but it was never merged.Related info:
The text was updated successfully, but these errors were encountered: