-
Notifications
You must be signed in to change notification settings - Fork 13
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
Type links are invalid #38
Comments
@eproxus, I'm not sure this is dealt with by the plugin. I also have a similar issue when using |
@starbelly, tested this again, and, as-is, this throws an exception with |
I will take a gander. |
Yeah, I'm also setting this up to see if it's easily fixable next to |
@paulo-ferraz-oliveira An example would be good, it works for me, but @eproxus is referencing a form with curly brackets, which I'm not familar with. Also, edoc complains saying |
Yeah, I can't get all of EDoc to work as per its documentation either. The form @eproxus is mentioning is indeed deprecated, but still supported by EDoc... |
Technically speaking |
Yeah, I'll let you decide on this one. If the |
The pull request mentioned above was merged. No further changes regarding I referred "Links are not usable, because generated HTML..." and ultimate we got "I'd strip out the <a> and just leave <code> but it definitely doesn't hurt to keep it this way for now." |
The mentioned pull request is already merged, tagged, released ( |
Didn't exactly understand what was said here. What would the alternative to |
@eproxus, there is no alternative, as of this moment.
So I don't think that, at least now, the plugin can move much more forward on this. |
When using the
{@type mytype()}
syntax, a link is generated to#type-mytype
but the ExDoc equivalent should be#t:mytype/0
it seems.The text was updated successfully, but these errors were encountered: