We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I like your gem, but it's seems very limiting that only one specific rake task can be run after changing several files.
It would be nicer to have something like this:
guard 'rake' do watch('db/seeds.rb') { 'db:seed' } end
The text was updated successfully, but these errors were encountered:
Okay, I just found out that it's possible to have many of these rake guards living next to each other:
guard 'rake' do watch('db/seeds.rb') { 'db:seed' } end guard 'rake' do watch('bla.rb') { 'bla' } end
Maybe you could point this out in the documentation. And still, somehow this feels more natural to me:
But maybe it's an (unwritten?) law that the block after watch(...) always only must return a path to a file...?
watch(...)
Sorry, something went wrong.
No branches or pull requests
I like your gem, but it's seems very limiting that only one specific rake task can be run after changing several files.
It would be nicer to have something like this:
The text was updated successfully, but these errors were encountered: