ppx_minidebug icon indicating copy to clipboard operation
ppx_minidebug copied to clipboard

Formatted logs of type-annotated let-bound values, function arguments and results, `if` and `match` branches taken. Optionally, as collapsible HTML or Markdown trees with highlights.

Results 28 ppx_minidebug issues
Sort by recently updated
recently updated
newest added

Entries that are definitely non-empty, but do not have any values logged at their level, are skipped -- only their children subtrees are logged. This is a reasonable design for...

I.e. every snapshot, and the final output, append to the `toc` files, -- potentially very long and definitely very misleading files.

bug

At least when the "location" (orphaned-from) is the only content of the entry.

bug

The overhead of tables on the size of generated HTML is non-trivial, assuming `~values_first_mode:true ~print_entry_ids:false` is going to be the most frequent setup. It would be nicer to just output...

Add a confing `` `Text { style: bool } `` and output hyperlinks if `style=true`.

enhancement

I wasted some time debugging, and only discovered the problem by switching to the flushing backend, where I got a nice stack trace.

bug

Add the ones that are possible, in particular `Nonempty_entries` is not but most levels are possible.

enhancement

They are standardized and error-case-specific. We could also print arbitrary exceptions but that might be too much noise.

enhancement

Use `Exclude_prefixed [||]` instead of `Prefixed [||]` for explicit-only logs.

enhancement