-
Notifications
You must be signed in to change notification settings - Fork 96
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
Renderers: allow for unqualified identifier rendering #636
Comments
First off: it's not specific to the HTML renderer. All those decisions are taken when translating the model into the document IR, so it's common to all renderer. Now, I mostly agree with you. We need to be careful about shadowing though. The tooltip idea is a good one. |
We've always intended to include Whilst it is definitely an ad-hoc rule, I'd be happy to use your suggestion for all |
I do think the |
I'd still like #594 be solved regardless of |
That sounds nice, but I don't think it would work well in presence of includes.
What would the doc of I think if we want something nice, we're going to have to keep track of currently opened modules, and do the shortening ourselves. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. The main purpose of this is to keep the issue tracker focused to what is actively being worked on, so that the amount and variety of open yet inactive issues does not overwhelm contributors. An issue closed as stale is not rejected — further discussion is welcome in its closed state, and it can be resurrected at any time. odoc maintainers regularly check issues that were closed as stale in the past, to see if the time is right to reopen and work on them again. PRs addressing issues closed as stale are as welcome as PRs for open issues. They will be given the same review attention, and any other help. |
I'm sure this is going to be controversial but I'll put it in to see what the mood is.
In general
odoc
html rendered specifications are much less readable than the.mli
they were generated from. The reason is that we get all the prefixes from the namespacing modules they belong to. This is precise but effectively, in a given context, these tend to become noise.I'd like to suggest to render identifiers mostly as they are found in the
.mli
, that is strip theopen
modules at most until the first prefix (so that we never get fully unqualified identifiers except for the built-in types).Following the links allows to make clear exactly what the identifier is about and optionally we could use a
name
attribute so that a tooltip reveals the fully qualified identifier.I'm sure people are going to suggest we could put that under a cli flag. I suggest we do not do so because in general when you devise docs you need a fair idea on how things are going to be presented.
A few things that are related to that:
open
#594Stdlib
prefix Remove Stdlib prefix #562The text was updated successfully, but these errors were encountered: