Added clean option to be able to use different naming conventions #40
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks! Merged, added specs and some info to the README. It's released with version 0.9.13. |
|
Cool, thanks! Sorry for not adding the specs! Anders On Wed, Feb 29, 2012 at 11:28 PM, Michael Kessler
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm using guard-jasmine outside of Rails and with a different naming convention
than in Rails. The specs are not in specs/javascript and are named differently.
In order to be able to use it anyway I added an option :clean, which defaults to true,
to avoid having my specs removed by the clean call.
If :clean is set to false the Inspect.clean method will not be called.
I will be very happy if you like to integrate it with your code.
Kind regards
Anders