-
Notifications
You must be signed in to change notification settings - Fork 325
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
Do not link to undocumented types #110
Comments
It looks like this is a problem with the autolinker, while it does check whether modules and functions exist in the current project it doesn't do so for types. |
I spent a little bit of time looking at this and here's what I found. Suspect you guys already knew most of it, but I'm going to say it out loud for my understanding. For the When Based on this, I don't see an easy way to catch this case. One option would be to allow doc pages to be created for these records. Or find some way to check |
Closing in favor of #192. |
Here: http://elixir-lang.org/docs/master/Version.html we link to the types
Version.Schema.t
andVersion.Requirement.t
. The types are not documented which is creating 404 links.We should make sure we are not creating 404 links and we could warn that we are referencing a type that is not documented.
The text was updated successfully, but these errors were encountered: