-
Notifications
You must be signed in to change notification settings - Fork 39
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
Detect import paths that only differ in capitalization #1295
Conversation
quint/cli-tests.md
Outdated
|
||
<!-- !test exit 1 --> | ||
<!-- !test check parse testFixture/_1060case.qnt - parse case sensitive filenames --> | ||
quint parse testFixture/_1060case.qnt |
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.
Should we also check if the error matches the expected? I think this test would pass even before your change.
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.
I also wanted to do that. But it's a bit hard to do, since the quint parse
outputs absolute paths.
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.
I've fixed this test by moving it to io-cli-tests.md
and comparing the outputs.
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.
left one comment, rest LGTM
Co-authored-by: Thomas Pani <[email protected]>
Co-authored-by: Gabriela Moreira <[email protected]>
I think I have addressed all of the comments. Please have a look |
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 👍
Closes #1194. This PR adds detection of filenames that use different capitalization. If this is the case, the parser flags an error. We have been discussing the option of storing hashes instead of normalized filenames, but this seems to be an overkill at the moment.
CHANGELOG.md
for any new functionality