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.

Sign up for GitHub

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

Jump to bottom

Improve error message when no .bloop folder is found #603

Closed
jvican opened this issue Aug 7, 2018 · 0 comments
Closed

Improve error message when no .bloop folder is found #603

jvican opened this issue Aug 7, 2018 · 0 comments
Labels
cli enhancement ergonomics Any change that affects developer ergonomics and the easiness of use of bloop.
Milestone
v1.1.0

Comments

@jvican
Copy link
Contributor

jvican commented Aug 7, 2018

@MasseGuillaume has suggested to improve the following error message when no bloop configuration files have been generated in a directory.

➜  backend git:(master) bloop about
[E] Configuration directory does not exist: /Users/jvican/Code/bloop/backend/.bloop

This is an excellent idea. We should just link to the installation docs whenever .bloop doesn't exist, and be more clear about what the user needs to do to fix it.
@jvican jvican added enhancement cli ergonomics Any change that affects developer ergonomics and the easiness of use of bloop. labels Aug 7, 2018
@jvican jvican added this to the v1.1.0 milestone Aug 7, 2018
jvican added a commit that referenced this issue Sep 12, 2018
@jvican
Add better feedback if configuration directory is missing
15341df 
Fixes #603
@jvican jvican mentioned this issue Sep 12, 2018
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
cli enhancement ergonomics Any change that affects developer ergonomics and the easiness of use of bloop.
Projects
None yet
Milestone
v1.1.0
Development

No branches or pull requests
1 participant
@jvican