Reload instead of run_all #8

Merged
tehpeh merged 1 commits from reload_instead_of_run_all into master 2011-10-18 13:29:44 +00:00
tehpeh commented 2011-10-17 23:11:32 +00:00 (Migrated from github.com)

Hi John,

This is what I meant regarding issue 6.

I've replaced run_all with reload so when a user hits return, nothing happens, but when they hit r+return the rails server restarts. This means you can use return to just run all tests, and r+return to restart rails, spork etc...

Any watched files will restart rails when touched, the same way it happens now.

What do you think? Does that work for you?

Hi John, This is what I meant regarding [issue 6](https://github.com/johnbintz/guard-rails/issues/6). I've replaced run_all with reload so when a user hits return, nothing happens, but when they hit r+return the rails server restarts. This means you can use return to just run all tests, and r+return to restart rails, spork etc... Any watched files will restart rails when touched, the same way it happens now. What do you think? Does that work for you?
johnbintz commented 2011-10-18 13:29:49 +00:00 (Migrated from github.com)

So I guess you're stacking your Rails runner and tests in one group/guard, then. I'll take a cue from guard-spork and support the same reload behavior, then. Consider your patch merged. :) Thanks for contributing!

So I guess you're stacking your Rails runner and tests in one group/guard, then. I'll take a cue from guard-spork and support the same reload behavior, then. Consider your patch merged. :) Thanks for contributing!
tehpeh commented 2011-10-18 22:32:49 +00:00 (Migrated from github.com)

Ok now I see. I was using different groups for a while, but now just run everything together. I run rails in daemon mode and tail the logs when I need to see what's going on.

Ok now I see. I was using different groups for a while, but now just run everything together. I run rails in daemon mode and tail the logs when I need to see what's going on.
Sign in to join this conversation.
No reviewers
No Label
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: github-migration/guard-rails#8
No description provided.