-
Notifications
You must be signed in to change notification settings - Fork 371
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve documentation generation #1892
Conversation
What differences do you see? Edit: regarding the "Basics" section being different -- when I build
No good method for this, unfortunately. You'd have to set up something that uploads the generated docs to somewhere yourself.
You can't at the moment. One issue is that trying to figure out the correct URLs is non-trivial (JuliaDocs/Documenter.jl#688).
Docstring missing warnings are for docstrings that you have already written, but are not being included on any manual page. So you should just add them into the manual to get rid of the warnings. E.g. the first docstring missing warning in the OP refers to this I believe: DataFrames.jl/src/abstractdataframe/show.jl Lines 239 to 275 in b0d8a87
These errors are somewhat unhelpful indeed. I think they all come from the "no doc found for X" errors. In that situation, Documenter just keeps the |
@mortenpi - a fantastic answer. Thank you! |
This should be good to merge (and test if all works OK again during deployment) |
Looks good |
Thank you. I need an approval before I can merge this. |
Done |
Thank you |
Fixes #1891
The original reason for this PR is #1891. The problem I have is that locally the documentation of the functions mentioned there is generated correctly, but it is broken on GitHub for some strange reason.
So I have started to look at documentation generation mechanics and fixed some deprecations. Currently when I build documentation locally I get the following output (sorry that it is long, but maybe something important is lurking there). I will ask the questions I have below the output.
Questions (maybe @mortenpi or @fredrikekre could give advice how to fix it - thank you for your support in advance 😄):
Question 1: why do I get different results locally and on remote when building the documentation (as I have said - the original problem locally is not present, but some other problems pop up that are not present on remote). What I should do to ensure that both are identical (as this is essential for testing for me)
Question 2: how can I check what documentation is generated remotely on GitHub during CI (but before merging the PR)
Question 3: I have a warning
Warning: duplicate docs found for 'DataFrame' in
@docsblock in src\lib\types.md:112-122
but I cannot see these duplicate docs - what is the reason of this warning?Question 4: I get warnings like (this is one example, there are many)
Warning: no doc found for reference '[
isequal](@ref)' in src\lib\functions.md.
- this is a reference to Base - how to make it work in a package? (so that I get a cross-reference from a package to Base)Question 5: I get warnings
Warning: 24 docstrings potentially missing:
- how can I indicate to Documenter.jl that I do not intend to write a documentation of some function (this is mostly needed for unexported or deprecated functionality or the functionality that extends Base; I know we have still some docstrings missing where they are needed 😢 - these will get added)Question 6: I get warnings like
Warning: invalid local link: unresolved path in lib\functions.md │ link = "@ref"
- how can I check which link is actually invalid (there are hundreds of them in the generated file)(sorry for the laundry list - if the answer is "read the Documenter.jl documentation" then please say so I will go through it again 😄 - I did it once, and did not notice the answers for these question)