Skip to content
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

UX improvement for typos in allow-newer #8426

Open
parsonsmatt opened this issue Aug 23, 2022 · 2 comments
Open

UX improvement for typos in allow-newer #8426

parsonsmatt opened this issue Aug 23, 2022 · 2 comments
Labels
attention: pr-welcome re: allow-newer Concerning `allow-newer` (option and field) type: enhancement

Comments

@parsonsmatt
Copy link

If I write this in my cabal.project file:

allow-newer:
    http-api-data:base
  , postgrseql-simple:base

then cabal doesn't complain, but it also tells me that the base version is Too New for postgresql-simple. It takes a minute to scan the text and realize my typo.

It'd be nice if allow-newer failed if the package name wasn't in the dependency set.

@Mikolaj Mikolaj added type: enhancement attention: pr-welcome re: allow-newer Concerning `allow-newer` (option and field) labels Aug 25, 2022
@Mikolaj
Copy link
Member

Mikolaj commented Aug 25, 2022

I took me 2 days and I'm still not certain: is the order of packages wrong in each pair? If so, a good idea to warn.

@ulysses4ever
Copy link
Collaborator

ulysses4ever commented Aug 25, 2022

@Mikolaj no, it's the name of package that is a problem: it has a typo. A more clear reproducer would be to say blah:base...

I wonder if this has been discussed before. Not clear to me that constraints that solver ended up not using should be an error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
attention: pr-welcome re: allow-newer Concerning `allow-newer` (option and field) type: enhancement
Projects
None yet
Development

No branches or pull requests

3 participants