master/Guardfile

ENV["GUARD_ENV"] = 'development'

guard('rspec', :cli => '-f doc', :version => 2) do
  watch(%r{^spec/(.*)_spec\.rb})
  watch(%r{^lib/(.*)\.rb})       { |m| "spec/#{m[1]}_spec.rb" }
  watch('spec/spec_helper.rb')   { "spec" }
end
Refactored Guard::Dsl#callback and updated specs, improved inline docs for Guard::Hook#hook, added ENV["GUARD_ENV"] = 'development' in Guardfile so we see hooks firing! Run specs on REE too. Signed-off-by: Rémy Coutable <rymai@rymai.me> 2011-04-29 22:40:12 +00:00			`ENV["GUARD_ENV"] = 'development'`

Run guards for new modified files only if any guard match any file (preventing from clearing the screen when no guard will run!). Signed-off-by: Rémy Coutable <remy@jilion.com> 2011-04-16 21:13:29 +00:00			`guard('rspec', :cli => '-f doc', :version => 2) do`
Guard no more automatically convert String into Regexp in "watch" method patterns. It allows to define: watch("foo_bar.rb") without meaning /foo_bar.rb/ (where "foo_bar_rb.rb" would have been matched) However, during the deprecation phase, strings that look like a regexes (e.g. "^foo_bar.rb", "foo_bar.rb$", "foo_.bar.rb" or "foo_(bar\|baz).rb" are converted automatically to Regexp and a very annoying* deprecation message is displayed. 2010-12-16 00:22:42 +00:00			`watch(%r{^spec/(.*)_spec\.rb})`
			`watch(%r{^lib/(.*)\.rb}) { \|m\| "spec/#{m[1]}_spec.rb" }`
			`watch('spec/spec_helper.rb') { "spec" }`
Refactored Guard::Dsl#callback and updated specs, improved inline docs for Guard::Hook#hook, added ENV["GUARD_ENV"] = 'development' in Guardfile so we see hooks firing! Run specs on REE too. Signed-off-by: Rémy Coutable <rymai@rymai.me> 2011-04-29 22:40:12 +00:00			`end`