relative_paths now defaults to false (issue #131) #133
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
…lse`, and added a mention of the errant change to the Changelog for v1.0.0 - Fixed minor mistake in the relevant spec (using `watched_directories` when should have been using `watched_directory` and tried to improve code to make similar mistakes more difficult to make. - Replace deprecated `mock` with new `double`, and fixed deprecated usage of `raise_error(SPECIFIC_ERROR_CLASS)` (see rspec/rspec-expectations#231)
thibaudgg
added a commit
that referenced
this pull request
Aug 14, 2013
relative_paths now defaults to false (issue #131)
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.
Listener#relative_pathsnow defaults tofalse, and added a mention of the errant change to the Changelog for v1.0.0watched_directorieswhen should have been usingwatched_directoryand tried to improve code to make similar mistakes more difficult to make.mockwith newdouble, and fixed deprecated usage ofraise_error(SPECIFIC_ERROR_CLASS)(see Consider deprecatingexpect { }.not_to raise_error(SpecificErrorClass)rspec/rspec-expectations#231)