forked from mongomapper/mongomapper
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fixed compatibility with edge rails (rails 3 master), with correspond…
…ing tests.
- Loading branch information
Fred Wu
committed
Mar 17, 2010
1 parent
34e6235
commit 6e5e531
Showing
2 changed files
with
30 additions
and
2 deletions.
There are no files selected for viewing
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
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
6e5e531
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works perfectly!
6e5e531
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is only with rails edge or something? I have not ran into this.
6e5e531
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jnunemaker: This is with Rails edge.
6e5e531
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jnunemaker: As geetarista stated above, this is a fix for the edge rails. Since one of the libraries I use (devise) requires edge rails, I think it makes sense to patch it up now. It does not effect v3.0.0.beta1 users. :)
6e5e531
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, this is an issue that only affects edge rails.
it looks like the form_for and similar refactoring is done, so i would say it is safe to patch it up.