This repository was archived by the owner on Oct 27, 2021. It is now read-only.
I could have fixed the bug on rspec I reported.#13
Open
norisuke3 wants to merge 1 commit intodchelimsky:masterfrom
Open
I could have fixed the bug on rspec I reported.#13norisuke3 wants to merge 1 commit intodchelimsky:masterfrom
norisuke3 wants to merge 1 commit intodchelimsky:masterfrom
Conversation
Owner
|
Clicking on the link to the report gets me a 404. What was the issue? |
|
The link Nori posted has some extra characters. This is the correct one: http://rubyforge.org/pipermail/rspec-users/2011-January/019187.html |
Author
|
Oops, sorry. Nori On Thu, Mar 31, 2011 at 11:56 AM, julio <
|
ghost
assigned
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
Hi David,
I could have fixed the bug on rspec I reported here: http://rubyforge.org/pipermail/rspec-users/2011-January/019187.html
I'm not sure if it's proper way to fix it or not, but it works for those explained in my report except the ControllerSpec one.
The ControllerSpec one might have a different reason because it's still indicating the same error on the test.
Anyway, please take a look at this patch, and if you agree with my update, please pull it.
Thank you,
Nori