Releases: aantron/bisect_ppx
Releases · aantron/bisect_ppx
Bisect_ppx 2.8.3
Additions
- ppxlib 0.28.0 and higher compatibility (#413).
- ReScript 10 support (#405, reported by Quinn Dougherty).
- ReScript 11 support (#422).
Bugs fixed
- Show sources of
.re
files in HTML view when build system is Dune (#404, reported by Konstantin Olkhovskiy). - Respect
[@coverage off]
in or-patterns (#414, reported by Nora Sandler). - Add
<packages>
to Cobertura format (#420, Maxim Grankin). - Stack overflow in HTML generation (#421, Allan Blanchard).
Changes
- Prebuilt binaries for npm are now built on Ubuntu 20.04 and macOS 11. They were previously built on Ubuntu 18.04 and macOS 10.
Bisect_ppx 2.8.2
Bisect_ppx 2.8.1
Bugs fixed
- OCaml 5.00 compatibility (#399, @kit-ty-kate).
Bisect_ppx 2.8.0
Additions
- HTML: collapsible tree index for large projects, activated by
--tree
option (#396, Arvid Jakobsson).
Bugs fixed
- Don't instrument lazy values which are compiled as already forced (#398, reported by @Ngoguey42).
- Use
Sys.backend_type
to detect js_of_ocaml (#397, Pat Rondon). - Text summary report: show files with 0 points as having 100% coverage (f3b9108).
Bisect_ppx 2.7.1
Bisect_ppx 2.7.0
Additions
- Reports in Cobertura XML format, used on GitLab (#383, Valentin Chaboche).
.coverage
file merging (#389, Valentin Chaboche).- Environment variable
BISECT_SIGTERM
and PPX option--bisect-sigterm
, which cause the runtime to write.coverage
files upon receiving SIGTERM (#390, Arvid Jakobsson). bisect-ppx-report
: verbose logging now hidden behind new--verbose
flag (4b36eb4).- HTML: minimal metadata so that links to reports are decorated by social media platforms (#373).
Bugs fixed
Bisect_ppx 2.6.3
Bugs fixed
- Downgrade binaries to require Ubuntu only 18.04, not 20.04 (6f86646, reported by Peter Piekarczyk).
Bisect_ppx 2.6.2
Changes
- Remove dependency on
Marshal
fromBisect_common
to adapt to upstream changes in ReScript (#376, reported by John Doneth).
Bisect_ppx 2.6.1
Bugs fixed
- Do not instrument
React.forwardRef
andReact.memo
(#375, reported by Mathieu Haton).
Bisect_ppx 2.6.0
Changes
- Port to ppxlib (#327, Sonja Heinze).
- CSS: use ligature fonts, if installed (#339).
- Internal: switch to Dune cram tests, finding lots of bugs in the process (beb80b3, 593a7c2, #352).
Bugs fixed
- Workaround for typing issue with instrumentation of or-patterns under GADTs; includes a new
match
instrumenter (#325, reported by Mehdi Bouaziz). - The second subexpression of
(||)
and(&&)
is in tail position iff the whole expression is in tail position; Bisect was unconditionally wrapping the second expression in successor code (#359, reported by Benjamin Monate). - HTML: words that have an instrumentation point on one of their characters were not searchable (#346).
- Don't clobber the global random number generator (#344).
(or)
nested inside(||)
not properly instrumented (#347).- Subexpressions of
Pexp_newtype
were always treated as if they were in tail position (#348). assert
instrumentation was placed at the wrong point in the generated code (#349).assert false
should not be instrumented; the point is unreachable (#355).- Instrumentation of or-patterns inside local
open
patterns could trigger unusedopen
warning (#350).
Removed
These removals were planned and announced in the 2.0.0 release.
- PPX option
--mode
(#200). - PPX option
--no-comment-parsing
(#202). - PPX option
--exclude
(#244). - PPX option
--exclude-file
, which has been renamed to--exclusions
(#245). - Reporter options
--html
,--text
,--coveralls
, which have been replaced byhtml
,summary
,send-to
subcommands, respectively (#145). - Support for discovering
.out
files. Bisect switched to extension.coverage
in 2.0.0 (#110). --dump
,--csv
, and the old-style text report (#251).- The old command line, including single-dashed (
-
) multi-character options, and usage ofbisect-ppx-report
without a subcommand (such asbisect-ppx-report html
) (#145).