-
Notifications
You must be signed in to change notification settings - Fork 97
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
HTML structure broken on master #631
Comments
Just to make things clear the HTML structure of a module is as follows:
The docs of a module should be allocated to these elements as follows:
|
If I understand correctly, this issue is related to #235 and both can be solved in the same way. These issues can be fixed by splitting the "composite top-comment" at the first heading, the first part goes into the preamble and the rest, starting from the first heading, in the content and is available in the TOC.
Odoc didn't have any code for handling synopsis 16 days ago, #597. |
Yes, but it's stop at first heading or structure item (ocaml specification).
Yes that's the same as what I suggested above. As mentioned there talking in terms of comments as unit doesn't really make sense, you want to talk in terms of blocks of the ocamldoc language.
My bad, apparently it does, but as seen in #628 in a confusing way. We suggested to change that a long time ago and nowadays it seems everyone agrees, see the discussion and further references in #597. |
Btw. that's not entirely true. It didn't have synopses for the Just to make sure: does that mean that we have two different code paths for that ? |
Odoc don't do synopsis (#632). |
This has been fixed by #640. |
It seems the merge of PR #627 broke the HTML structure. See the comment here.
The text was updated successfully, but these errors were encountered: