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

Fix #460 - findNimbleFile 'not found' error more specific #859

Merged
merged 2 commits into from Oct 19, 2020
Merged

Fix #460 - findNimbleFile 'not found' error more specific #859

merged 2 commits into from Oct 19, 2020

Conversation

romanthekat
Copy link
Contributor

@romanthekat romanthekat commented Oct 10, 2020

Not found error updated to Specified directory ($1) does not contain a (*).nimble file. from Specified directory ($1) does not contain a .nimble file..
That probably specifies more explicitly that 'SOMETHING.nimble' is required, thus help to not get confused with scenarios like .nimble file not being acceptable.
Not sure whether it is an actually useful change.

Besides that, errors nearby like Only one .nimble file should be present in could have probably being updated too, but it wasn't mentioned in #460, so didn't try to update it in this PR

@romanthekat romanthekat changed the title Fix #360 - findNimbleFile 'not found' error more specific Fix #460 - findNimbleFile 'not found' error more specific Oct 10, 2020
Copy link
Collaborator

@dom96 dom96 left a comment

Choose a reason for hiding this comment

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

How about instead you change it to: "Could not find a file with a .nimble extension inside the specified directory: $1"?

@romanthekat
Copy link
Contributor Author

How about instead you change it to: "Could not find a file with a .nimble extension inside the specified directory: $1"?

Sounds great, added

@dom96 dom96 merged commit b4f2954 into nim-lang:master Oct 19, 2020
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.

None yet

2 participants