Clarify difference between lsp and hie-bios configuration

[lukel97]

Do this by renaming explicit configuration to project configuration

[fendor]

Can we also explain that we prefer cabal projects over stack projects at the moment? Or should we rather not?

[lukel97]

@fendor in what ways do we we prefer cabal projects?

[fendor]

if there is a cabal.project and a stack.yaml we select a cabal project.

[jneira]

if there is a cabal.project and a stack.yaml we select a cabal project.

for completeness, if cabal is available

i think hie-bios would choose plain ghc under some conditions, right?

[lukel97]

@fendor but if there is no cabal.project and a stack.yaml, then cabal-helper selects a stack project! And a cabal.project is not necessary for cabal v2 builds. I'll add a table documenting this

@jneira

i think hie-bios would choose plain ghc under some conditions, right?
If neither cabal nor stack is on the path I presume

[fendor]

@jneira no, hie-bios only chooses the cradle based on hie.yaml, we are not using the implicit configuration and c-h only chooses between cabal and stack.

@bubba I think with neither *.cabal file nor stack.yaml, we do not find a project context and we are selecting a none-cradle.

[alanz]

The old behaviour if there was both a stack.yaml and cabal.project was to look for dist or .stack-work, and choose based on that if there was only one. Fallback to whatever.

[fendor]

We should add that back, but currently we are definitely using the cabal v2-cradle if there is both.

[alanz]

I think the break decision where both are present is arbitrary, there is a hie-bios config file after all, but when it is not present falling back to what the user has at that time does make sense.

[fendor]

Should we add this feature after merge or in a consecutive pr?
I think a subsequent pr would be fine.

[alanz]

After merge is fine

[lukel97]

@fendor would it be worthwhile to (sometime after the merge) select the direct cradle in these cases?