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

Bloop should indicate when --watch is waiting for source changes #422

Closed
olafurpg opened this issue Apr 7, 2018 · 4 comments
Closed

Bloop should indicate when --watch is waiting for source changes #422

olafurpg opened this issue Apr 7, 2018 · 4 comments
Labels
ergonomics Any change that affects developer ergonomics and the easiness of use of bloop. good first issue help wanted

Comments

@olafurpg
Copy link
Contributor

olafurpg commented Apr 7, 2018

I ran bloop test --watch tests-test in the metadoc repo and when the tests complete the last line that is printed out is

- .semanticdb.json

It would be nice if that line was followed with some message from bloop indicating that bloop is waiting for more source changes, something like

Waiting for source changes... (press ??? to interrupt)
@jvican jvican added help wanted good first issue ergonomics Any change that affects developer ergonomics and the easiness of use of bloop. labels Apr 7, 2018
@jvican
Copy link
Contributor

jvican commented Apr 7, 2018

Thanks for the ticket! @rberenguel you may wanna be interested in this ticket too, fix should be two lines of code 😄 ^^

@rberenguel
Copy link
Contributor

@jvican :D I will, I'm still getting used to the development cycle for bloop

@rberenguel
Copy link
Contributor

@olafurpg @jvican I can't reproduce this locally, I get File watching 28 directories... as last message when watching on tests or compile the same.

@rberenguel
Copy link
Contributor

Oh, got it now, the message only appears on first run, does not get repeated on file modified

jvican added a commit that referenced this issue Apr 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ergonomics Any change that affects developer ergonomics and the easiness of use of bloop. good first issue help wanted
Projects
None yet
Development

No branches or pull requests

3 participants