-
Notifications
You must be signed in to change notification settings - Fork 131
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
Make it easier to fix "direct dependencies" error message #776
Comments
I believe this was fixed in #770? |
Ah right sorry, looks like it does indeed - I used the latest release but didn't check the unreleased fixes. Does the last paragraph look feasible?
|
Thank you @f-f - closing |
You're welcome 🙂 |
I was thinking that it could be handy if the list of packages that is shown for the following error would instead contain lines that can directly be copy-pasted into
spago.dhall
(rather than having to edit after paste) or, even better ifspago
would ask if it's ok to apply the necessary changes tospago.dhall
The following warning may also be incorporated in the suggestion, though this is less work to do manually:
A step further and not sure how easy this would be to implement, but it would be awesome if
spago
could also apply the addition of new dependencies in the same way (as long as it's in the package set). I.e. if it would recognise the package that needs to be added given a certain import that was just added.The text was updated successfully, but these errors were encountered: