-
-
Notifications
You must be signed in to change notification settings - Fork 367
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
feat(hie-bios): Multi-cradle, ignore directories #147
Conversation
* Add stack.yaml to install/ folder * Add Stack and Cabal templates for hie.yaml for install/ folder * Add and cleanup documentation about hie.yaml * Add comment about building for Stack
d6c69a4
to
27d3557
Compare
I've test the changes and i have to say that i was wrong about the none cradle: it is not supported by ghcide yet (see https://github.com/digital-asset/ghcide/issues/258). Testing it in with hls in cli mode confirms that, cause it still tries to load modules under testdata EDIT: i've tested it again in a simple stack project with |
@jneira I've gotta say I am confused by your message 😄 It works fine for me. E.g. hovering on any function in the This looks exactly like the expected behavior to me 🤔 |
I was guessing that it works for you, but i wanted to confirm it cause i cant get it working for me (maybe it is a windows issue?) |
@@ -0,0 +1,13 @@ | |||
resolver: lts-14.27 # Last 8.6.5 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we could use only one stack.yaml
, removing shake.yaml
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it still wouldn't AFAIR there were inconsistencies with the Cabal dependency (not 100% sure though). But as long as there's a dependency on Shake, we can't do much...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mmm not sure what was the problem, but i've tried:
- add
flags:
hls-install:
run-from-stack: true
to ./install/stack.yaml
- remove
./install/shake.yaml
- replace in
./install.hs
,--stack-yaml=install/shake.yaml
with--stack-yaml=install/stack.yaml
And both stack install.hs <target>
and opening ./install/src/BuildSystem.hs
seems to work fine.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sir4ur0n we could do the suggested change above in another pr if you prefer and merge this as is
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not in hurry since I currently don't work with files under /install
directory, and somehow managed HLS to work with itself in other directories, so please do whatever you are in favor of.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Ailrun sorry, bad mention 😅
No luck, hls continue trying to load all files under
But, well. the config itself is correct and we could investigate later why it does not work in my env |
Do you test with the Cabal or the Stack HIE file? I only test with Stack (in WSL1 as you already know). Would be good to identify the discrepancy between your tests and mine. That being said, if you're ok with this PR, we can also merge it and keep investigating in another issue. The scenarii we know:
For what it's worth, my logs for opening the exact same file:
Note in particular:
|
Yeah, the weird thing is the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, i am going forward and merge this one. I'll unify install/shake.yaml and install/stack.yaml in a new pr.
These tests document and monitor the evolution of the capabilities announced by the server in the initialize response. Currently the server advertises almost no capabilities. Out of 23 top-level categories, the only 3 which are announced are + text document sync + hover + goto definition At the very least code actions are known to be provided, but are not announced in the initialize response.
testdata
)Closes #121
Closes #145
Note: Because my personal computer runs on Windows + WSL1 + there is a bug with WSL1 + Cabal, I can't test the Cabal flavor.
If anybody would be kind enough to give it a try, I would appreciate 😄