github-migration/master
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
344 Commits 6 Branches 30 Tags 1 MiB
694664ced8
Commit Graph

18 Commits

Author SHA1 Message Date
Thibaud Guillaume-Gentil
ba0b84838d Integrated Guard::Ego inside Guard, oh yeah! 2011-07-02 10:01:45 +02:00
Tim Pope
524af462d9 Make home Guardfile hidden 2011-06-22 10:54:50 -04:00
John Bintz
b0d30900fb add additional spec to test string-only guard group names 2011-06-01 15:00:01 -04:00
John Bintz
087f51085f allow symbols for group names 2011-06-01 14:17:31 -04:00
Thibaud Guillaume-Gentil
1747f66128 Merge branch 'user_guardfile' of https://github.com/hashrocket/guard into hashrocket-user_guardfile 
Conflicts:
	lib/guard/dsl.rb
	spec/guard/dsl_spec.rb
 2011-05-28 17:52:50 +02:00
Rémy Coutable
b471405f4d Merge branch 'master' of https://github.com/anithri/guard into anithri-master-55 
Conflicts:
	lib/guard/notifier.rb
	spec/guard/dsl_spec.rb
	spec/guard/listeners/polling_spec.rb
	spec/guard/notifier_spec.rb
 2011-05-27 17:56:18 +02:00
Aaron Kalin and Veezus Kreist
9928f80c76 Fix guardfile_path spec for Windows support 2011-05-25 13:32:56 -05:00
Aaron Kalin and Veezus Kreist
add80d2831 Conform to project standards 2011-05-25 13:23:02 -05:00
Joshua Davey and Veezus Kreist
debdecbbd7 Allow user-based Guardfiles 2011-05-24 16:44:24 -05:00
Michael Kessler
5f0c815256 Cleaning up all specs. 
I basically went through all specs and applied the following rules:

* Use `describe` for methods and `context` for contexts.
* All class methods starts with `.` and instance methods with `#`.
* Removed all `it should`, because the specs _have to_.
* Applied a consistant naming on all listener specs.
* Make fixture usage more fail save by giving generous sleep times.
* Make all behaviour description non-technical and easy to understand.

The goal of this excercise was to have a documentation that is easy
readable and describes the behaviour and not the implementation.

Try it out by using the RSpec documentation format!
 2011-05-13 11:26:05 +02:00
Scott Parrish
8ea296bf8f Guard::Dsl changed massively. overall strategy was to decouple to evaluate_guardfile into "getting the data" and "using the data" parts. this provides the ability to pass a string that contains the contents of a guardfile, or to pass a filename for a guardfile as well as reading the default loc for a guardfile. 
Dsl specs changed massivly to support new style of Dsl
 2011-05-06 20:53:34 -06:00
Rémy Coutable
9b981f5459 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 23:13:29 +02:00
Thibaud Guillaume-Gentil
42c27242e1 Added a command line option (-n false) to disable notifications (growl/libnotify). closed #28 2011-04-10 22:32:29 +02:00
Rémy Coutable
a0f1ac4053 Renamed Guard::Dsl.guardfile_included? to Guard::Dsl.guardfile_include? (private API) and fix a bug where Guard::Dsl.guardfile_include? was not detecting guard specified with a symbol, double quotes or parenthesis in Guardfile. 
e.g.:
guard :rspec
guard ('rspec')
guard("rspec")
...
 2010-12-17 18:37:44 +01:00
Rémy Coutable
f90823ae90 Shortened implementation of the new group DSL method and made it (+ specs) clearer 2010-12-17 18:13:31 +01:00
Michael Kessler
63af219490 Enhance the DSL to allow grouping of guard definitions and run them selectively 2010-12-17 16:31:39 +01:00
Rémy Coutable
39ea8441c0 Avoid using actual fixture files, instead mock Guardfile content (this way we can directly see tested Guardfile content in the specs. 2010-10-30 22:42:17 +02:00
Olivier Amblet
dd1100b4ae Added DSL specs and improved error message. 
DSL now have basics specs that confirm it works
I splitted file not found and invalid Guardfile
error message because it was confusing to know
in which case you are when it occurs :)
 2010-10-30 18:26:09 +02:00