Skip to content
This repository has been archived by the owner on Jan 2, 2021. It is now read-only.

Upgrade to hie-bios 0.3 #257

Merged
merged 1 commit into from
Dec 16, 2019
Merged

Upgrade to hie-bios 0.3 #257

merged 1 commit into from
Dec 16, 2019

Conversation

cocreature
Copy link
Collaborator

This does not yet take advantage of any new features but we should at
least be able to benefit from bugfixes.

This does not yet take advantage of any new features but we should at
least be able to benefit from bugfixes.
@cocreature cocreature changed the title Upgrade to hie-bios Upgrade to hie-bios 0.3 Dec 16, 2019
@mpickering
Copy link
Contributor

Note that anything configured with the multi-cradle will also not work with ghcide because you pass the empty path when trying to determine which component to use.

@cocreature
Copy link
Collaborator Author

Right but that was already the case before. Multicomponent cradles definitely don’t work at the moment.

@cocreature cocreature merged commit fc30f14 into master Dec 16, 2019
@cocreature cocreature deleted the bump-hie-bios branch December 16, 2019 10:42
@symbiont-eric-torreborre

Right but that was already the case before. Multicomponent cradles definitely don’t work at the moment.

This deserves a bigger note in the release notes, I was wondering what I was doing wrong :-). Is it still possible to load only the modules from one of the components though?

@cocreature
Copy link
Collaborator Author

If you set your hie.yaml to a cabal cradle that loads one component it should work fine (see https://github.com/mpickering/hie-bios#explicit-configuration). You can also manually construct a direct cradle that merges the components and sets things like default extensions and include paths manually (getting packages can be a bit tricky but the ghc environment files that cabal writes by default should be picked up).

@domenkozar
Copy link
Contributor

I think previously by default stack would load lib and exe components, whereas with the upgrade I can only specify one component (since multi-cradle isn't supported yet). Is that correct observation?

@cocreature
Copy link
Collaborator Author

As far as I know cradle: { stack: {}} should be equivalent to the stack cradle on older hie-bios versions.

@domenkozar
Copy link
Contributor

That's what I thought, but hie-bios fails since stack asks to pick the component between lib, exes and tests.

@cocreature
Copy link
Collaborator Author

Not sure what is going on then. Maybe worth opening an issue in hie-bios for that.

@fendor
Copy link
Collaborator

fendor commented Jan 13, 2020

We no longer pass in filepaths to stack repl but components which likely explains this behaviour. If you are not using a component, just stack repl is used, which asks to pick the component if there are multiple exes, for example.

@cocreature
Copy link
Collaborator Author

We never did pass a file path in ghcide, we just set that to an empty string so I’m still struggling to see what changed here. Could it be that this never worked if you have more than one main module?

pepeiborra pushed a commit to pepeiborra/ide that referenced this pull request Dec 29, 2020
This does not yet take advantage of any new features but we should at
least be able to benefit from bugfixes.
pepeiborra pushed a commit to pepeiborra/ide that referenced this pull request Dec 29, 2020
This does not yet take advantage of any new features but we should at
least be able to benefit from bugfixes.
pepeiborra pushed a commit to pepeiborra/ide that referenced this pull request Dec 29, 2020
This does not yet take advantage of any new features but we should at
least be able to benefit from bugfixes.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants