Import Haskell module or automatically import new Cabal packages
See original GitHub issueRepro:
- Have a multi-package Stack project handled with IJ-haskell
- Create another cabal package inside it and specify it in
stack.yaml
- Open above project in IDEA
Expected: new cabal package gets picked up by IJ-haskell, the way it got picked up when importing project
Instead: it is not. In order to pick up new cabal packages user has to reimport project losing custom modules, local history, configurations etc.
Issue Analytics
- State:
- Created 5 years ago
- Comments:28 (28 by maintainers)
Top Results From Across the Web
4.1. Quickstart — Cabal 3.4.0.0 User's Guide
Cabal takes the approach that all packages dependencies are specified explicitly and specified in a declarative way. The point is to enable automatic...
Read more >How do you import a Haskell module that was installed using ...
1 Answer 1 · Make a cabal package and add timezone-series you want to install to the build-depends field as described in the...
Read more >Cabal User Guide: Developing Cabal packages
For a library, cabal init looks in the project directory for files that look like Haskell modules and adds all the modules to...
Read more >4.9. Packages - Haskell.org Downloads
All you need to do is write a simple configuration file, put a few files in the right places, and you have a...
Read more >5.9. Packages — Glasgow Haskell Compiler 9.4.1 User's Guide
Only modules from exposed packages may be imported by your Haskell code; if you try to import a module from a hidden package,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Not really, it was that huge project on the job. Will try to reproduce the issue against the sample project bit later.
Done in beta43. It only adds/imports new modules.