You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Inside the cabal and stack folders, there's an ambiguity as to what directory it should pick for the cradle: it can either choose the more local nested one or the stack.yaml in the upper directory.
In the cabal folder:
This means that stack will always win over cabal if it can find a stack.yaml in any upwards directory.
What I would have expected would be for both cabal.project and stack.yaml to be searched for in the current directory, before peeking in the parent directories. Thoughts?
The text was updated successfully, but these errors were encountered:
This is open to discussion, not really a bug as much as potentially surprising behaviour. Consider the following directory structure:
Inside the
cabal
andstack
folders, there's an ambiguity as to what directory it should pick for the cradle: it can either choose the more local nested one or thestack.yaml
in the upper directory.In the
cabal
folder:That seems fair enough, it's choosing the more global stack project.
But in the
stack
folder:It chooses the more local folder!
This isn't a bug but rather just how the implicit cradle search is done:
This means that stack will always win over cabal if it can find a stack.yaml in any upwards directory.
What I would have expected would be for both
cabal.project
andstack.yaml
to be searched for in the current directory, before peeking in the parent directories. Thoughts?The text was updated successfully, but these errors were encountered: