odoc icon indicating copy to clipboard operation
odoc copied to clipboard

Documentation compiler for OCaml and Reason

Results 130 odoc issues
Sort by recently updated
recently updated
newest added

The comments are not rendered in this example: ```ocaml type bar = < > type t = < foo : int; (** foo *) bar (** bar *) > ```

bug
output

Following up on https://github.com/ocaml/odoc/issues/875 it seems that comments do get lost on current master. Below the include in `B` has no docs. The include in `A` does. ``` > cat...

bug
output

The functor `App` in the following does not produce an expansion: ```ocaml module type Type = sig module type T end module App : functor (T : Type) (F :...

stale

Hello, method types generated in documentation are incorrect, they include the implicit object parameter. For example, with the following definition: ```ocaml class foo = object method bar = 1 end...

bug

Root: ```ocaml module Foo : sig val x : int end module Bar : sig val x : int end ``` Test: ```ocaml module Root : sig module Foo :...

not stale

Considering a polymorphic variant type: ```ocaml type switch = [`On; `Off] ``` I'd like to be able to refer to the constructors in the documentation. It could be doable if...

cross-referencer
enhancement

I put example code for this at https://github.com/leviroth/odoc-bug-demo. The crux of the example is that I have, in `p.mli`: ``` type t = private int module M : sig type...

stale

We would like to be able to render to a markdown document.

not stale

``` > echo "{0:sample OCaml 4.11.1 sample package documentation}" > frag.mld > odoc html-fragment frag.mld OCaml 4.11.1 sample package documentation ``` This breaks the `odig odoc --index-intro` option used e.g....

bug
output

The comment `bar` isn't rendered in this example: ```ocaml type bar = [ `Bar ] type t = [ `Foo (** foo *) | bar (** bar *) ] ```

bug
output
good-first-issue