Hyperlink types in type signatures about package.elm-lang.org HOT 6 CLOSED

See https://groups.google.com/d/msg/elm-discuss/7JJyM1UkXsQ/vRGGaKQMayAJ.

from package.elm-lang.org.

I've implemented this: #60

from package.elm-lang.org.

@agrafix, maybe close this issue, or replace it with something describing what is desirable on top of #60 (which has been merged and is live on the package site).

from package.elm-lang.org.

Cool, thanks for your work! It does not work everywhere yet though? ( http://package.elm-lang.org/packages/elm-lang/core/2.1.0/Regex#find ). And it does not work across packages yet, correct? This is probably a compiler limitation?

from package.elm-lang.org.

1. It only works (and will only ever work) for packages that are published with the now current Elm suite or later ones. The example package you give was either uploaded a while ago, or was uploaded recently but with outdated tools. The difference can be seen in the last entry of http://package.elm-lang.org/packages/elm-lang/core/2.1.0/docs/Regex.json. Whenever such a file has "generated-with-elm-version": "old", it won't profit from the type hyperlinking.
2. And yes, it does not work across packages, and indeed that is because there is not enough information in the .json files. It would have to be put there by the compiler or upload tool. Prior to that, some design decisions would have to be made. Quoting Evan from the mailing list message already linked to above:

Doing it across packages is harder, because we do not have the package annotations there right now. So I'd say do it within first, then we can think about questions like, "when linking to another package, which version do I link to? Highest in declared bounds? The one the author was using?"

from package.elm-lang.org.

Agree with @jvoigtlaender, if further things are desired, open an issue describing it so we have a clean issue to look at.

from package.elm-lang.org.