Skip to content
This repository has been archived by the owner on Oct 5, 2022. It is now read-only.

Ability to "Go to Declaration" for project dependencies #17

Open
nhenin opened this issue Apr 6, 2018 · 1 comment
Open

Ability to "Go to Declaration" for project dependencies #17

nhenin opened this issue Apr 6, 2018 · 1 comment

Comments

@nhenin
Copy link

nhenin commented Apr 6, 2018

Hi,

Hasktags seems to only generate tags for internal modules and not for my external dependencies...
Is it possible to "Go to Declaration" in atom for external dependencies and see the code source ?

P:S : I found Haskdogs that seems to generate these tags into a tag file (root directory) but your plugin doesn't seem to read this file...

Thank you.

@lierdakil
Copy link
Contributor

lierdakil commented Apr 6, 2018

Hi. Thanks for the report. Unfortunately, the reply might not be to your satisfaction.

If you want to use TAGS file, just use Atom's symbols-view. The whole point of this package (that is, ide-haskell-hasktags) is to have a "batteries included" solution -- as a consequence, there are some limitations. If you're fine with running hasktags or similar once in a while to update the TAGS file, you don't really need this package.

In general, Haskell package dependencies are compiled, and sources are not readily available and need to be pulled in separately (with stack unpack or similar). So there's no "silver bullet" per se.

Haddock (and, f.ex., ide-haskell-hoogle) might provide an alternative via showing Haddock documentation (which can optionally show source code in most cases) -- it's a bit rough around the edges though, so feel free to open bug reports and/or feature requests. Note that if you want to use a local Hoogle database, you'll need to build it first (via stack hoogle etc, and it might take a while)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants