Skip to content

Conversation

@sol
Copy link
Owner

@sol sol commented Jan 20, 2021

No description provided.

@sol sol force-pushed the warn-on-invalid-modules branch from b7b1649 to 7c25383 Compare January 20, 2021 18:41
Foo
Bar
Baz
|] `shouldWarn` ["package.yaml: invalid module name \"Foo Bar Baz\" in $.library.other-modules"]
Copy link
Contributor

@andreasabel andreasabel Jan 21, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Couldn't users be surprised that they are warned about an invalid module name, but then things "work fine" in the sense that a working cabal-file is produced?
#421 (comment)

So maybe the warning should add that things might work by accident nevertheless, but in the future this behavior will not be supported any more.

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I think you have a point. I think what we want is tell the user what to do (say turn it into a YAML list). I'll look into it.

@sol sol force-pushed the warn-on-invalid-modules branch from 7c25383 to f9f91b8 Compare February 3, 2021 06:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants