You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Take, for instance, this example in diagrams-core. Here a module reference refers to a module in diagrams-lib which the diagrams-core does not itself depend upon (in factor diagrams-lib depends upon diagrams-core). It would be great if there were a way to qualify a module reference with a package name.
The text was updated successfully, but these errors were encountered:
It would be great if there were a way to qualify a module reference with a package name.
We can't refer to something that can't find and understandably, we can't find a module that is not imported and worse, has a dependency on the package we're building so I'm not quite sure how such a feature would look like. The only reason the module name you gave is even a link is because we default to a module within same package if we don't know where the module actually is.
I think unless you're able to pass diagrams-lib package as one of the packages during doc creation, you're out of luck. You might use a hack and just embed a regular link pointing to relative path of the diagrams-lib docs on Hackage. I think such a hack would be the best we could do ourselves. I'm not going to close the issue yet because I want to investigate how passing in such an extra package argument would look like so that maybe we can streamline the process somehow.
Take, for instance, this example in
diagrams-core
. Here a module reference refers to a module indiagrams-lib
which thediagrams-core
does not itself depend upon (in factordiagrams-lib
depends upondiagrams-core
). It would be great if there were a way to qualify a module reference with a package name.The text was updated successfully, but these errors were encountered: