Fix for Rails 3.1 Timestamp Generation & Psych YAML Parse Errors #10
Conversation
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
…eturn value in method_missing overload. fixes winton#8
winton
pushed a commit
that referenced
this pull request
Nov 12, 2011
Fix for Rails 3.1 Timestamp Generation & Psych YAML Parse Errors
Owner
|
Thanks for the contrib! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Since upgrading to Rails 3.1 migration generation has failed to include the timestamp portion of the filename. This was due to a discarded return value in the method_missing overload used to hook into the migration generator. This patch ensures that the return value is returned to the caller and fixes issues installing via Bundler under Ruby 1.9.x due to Psych parse errors.