Jon Ludlam
Jon Ludlam
I'm not sure it's the same cause, because every single version of odoc is failing with the same error, and ocurrent/solver-service#61 looks less reproducible.
I suspect we need two things: 1. For dune to grow the ability to build docs for pre-installed packages 2. For this process to distinguish between running odoc on pre-installed...
https://github.com/ocaml-doc/voodoo/pull/126 addresses this hopefully.
Thanks for reporting this! It does indeed look like our issue. I'll take a look and see what's required to fix this.
You mention "library interface files" `Lib.ml` and `Lib.mli` - are you building with `dune` and is your library by any chance named `lib`? If so, try naming the library something...
OK, so that explains why you're seeing that behaviour. Odoc will inline includes if doesn't know of a non-hidden path to the module/type being included. In this case there's no...
Ah that sounds familiar. I wonder if this fixes it? https://github.com/jonludlam/odoc/commit/3b8b9258e4cc6f6e5c9dfac50188ba87e82ca72e
The dune rules haven't yet been updated for odoc 3. Try using `odoc_driver` - you can either install the package and run `odoc_driver ` or you can run it from...
I think it'd be useful to have some tests for the changed functionality in odoc itself.
I'm also happy with 4 - though it's worth mentioning that any instance of `[` in the text will turn it into a code block, so we may need to...