# Missing docstrings with Documenter

**URL:** <https://discourse.julialang.org/t/missing-docstrings-with-documenter/29122>\
**Category:** General Usage\
**Tags:** documenter\
**Created:** [September 24, 2019, 5:27pm UTC](https://discourse.julialang.org/t/missing-docstrings-with-documenter/29122 "2019-09-24T17:27:43Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![pulsipher](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pulsipher/32/10461_2.png) [@pulsipher](https://discourse.julialang.org/u/pulsipher)\
**Post date:** [September 24, 2019, 5:27pm UTC](https://discourse.julialang.org/t/missing-docstrings-with-documenter/29122/1 "2019-09-24T17:27:43Z")

</div>

I am building documentation for my package [InfiniteOpt.jl](https://github.com/pulsipher/InfiniteOpt.jl), but I have 4 docstrings that Documenter cannot find for some reason. These correspond to the last 4 function references I make on my Model Transcription page (docs/src/guide/transcribe.md) in a `@docs` block. These correspond to docstrings for particular typed versions of the functions `InfiniteOpt.supports` and `InfiniteOpt.parameter_refs`. These typed versions are defined in a submodule (`TranscriptionOpt`) (they are defined in src/TranscriptionOpt/model.jl) and show up using the ? help search in the REPL, but Documenter can’t find them. What is even weirder is there are 2 other typed versions of `InfiniteOpt.supports` with docstrings defined in the same submodule that are picked up by Documenter without issue.

All of the other docstrings defined in the `InfiniteOpt` and `InfiniteOpt.TranscriptionOpt` are detected without issue, but I can’t get Documenter to find these 4 docstrings no matter what I try. I have also tried adding an `@meta` block that calls `using InfiniteOpt` as described [here](https://stackoverflow.com/questions/50768111/julia-documenter-missing-docstring) to no avail.

I realize it is preferable to provide a minimal working example of the problem, but I am having difficulty reproducing it. I would very much appreciate any help figuring out what is wrong. Thanks!

---

<div class="post-metadata">

**Author:** ![mortenpi](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mortenpi/32/158_2.png) [@mortenpi](https://discourse.julialang.org/u/mortenpi)\
**Post date:** [September 24, 2019, 11:23pm UTC](https://discourse.julialang.org/t/missing-docstrings-with-documenter/29122/2 "2019-09-24T23:23:44Z")

</div>

The signatures must match exactly. Do you actually have these methods (with docstrings; from [here](https://travis-ci.com/pulsipher/InfiniteOpt.jl/jobs/238718316#L259-L330)) anywhere?

```julia
InfiniteOpt.supports(::JuMP.Model, ::InfiniteOpt.GeneralConstraintRef)
InfiniteOpt.supports(::InfiniteOpt.GeneralConstraintRef)
InfiniteOpt.parameter_refs(::JuMP.Model, ::InfiniteOpt.GeneralConstraintRef)
InfiniteOpt.parameter_refs(::InfiniteOpt.GeneralConstraintRef)

```

---

<div class="post-metadata">

**Author:** ![pulsipher](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pulsipher/32/10461_2.png) [@pulsipher](https://discourse.julialang.org/u/pulsipher)\
**Post date:** [September 24, 2019, 11:45pm UTC](https://discourse.julialang.org/t/missing-docstrings-with-documenter/29122/3 "2019-09-24T23:45:05Z")

</div>

Aha, now that I look at it again with fresh eyes I see that the second argument should be `InfiniteOpt.InfiniteConstraintRef` not `InfiniteOpt.GeneralConstraintRef`. Just a bug stemming from an old change in the docstring I forgot about. I thought it was probably something fairly minor. Thank you, for your time.