-
Notifications
You must be signed in to change notification settings - Fork 704
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
cabal init -i should sanitize suggested package name (fix #8404) #8561
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. were tests not affected? if so it would be good to have a regression against this.
Well, tests are failing currently, so I'll have to take a look. |
b04c6e7
to
76f91dd
Compare
fc8e309
to
26a3f78
Compare
Ready for review! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - thanks for the regression.
@mergify backport 3.8 |
✅ Backports have been created
|
* cabal init -i should sanitize suggested package name (fix #8404) * fix existing tests * fix more tests (golden) * fix more tests (generators, simple) * add regression test * add changelog Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> (cherry picked from commit e714824)
… (haskell#8561) * cabal init -i should sanitize suggested package name (fix haskell#8404) * fix existing tests * fix more tests (golden) * fix more tests (generators, simple) * add regression test * add changelog Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
An easy fix for #8404: cabal init -n already does the right thing, so this PR merely moves some code around so that cabal init -i can benefit from it too.
Please include the following checklist in your PR:
Please also shortly describe how you tested your change. Bonus points for added tests!