-
Notifications
You must be signed in to change notification settings - Fork 22
Support guard-rspec (4.0.4) #26
Comments
Same problem. And I don't know, where is this -f argument. Has anyone any thoughts? |
Having this issue too. See guard/guard-rspec#167 as well. |
When my .rspec file contained
|
👍 |
Having this issue as well - |
Just using regular rspec under guard until this is resolved. I looked through the code but was pretty lost. |
My above pull request to guard-rspec was just accepted; so here's a workaround until there's a better fix - use the following options:
This'll wrap all the normal options and then append the specs to run, e.g.
|
I am (as of a few days ago) the new maintainer for this gem, and I'm looking through the old issues now. Do you still need to use the workaround you mentioned? If so, I'll add it to my queue to develop a more long-term fix. If not, feel free to close this issue. |
I'm no longer using this gem. |
In later versions of guard-rspec the
zeus
,bundle
andparallel
options are depreciated:Guard::RSpec DEPRECATION WARNING: The :zeus option is deprecated. Please customize the new :cmd option to fit your need.
However if I invoke rspec_parallel in my Guardfile
It fails as Guard appends the -f argument.
The text was updated successfully, but these errors were encountered: