Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Solves problems between MongoMapper and brute_force_protection. #195

Merged
merged 2 commits into from
Jan 24, 2012
Merged

Solves problems between MongoMapper and brute_force_protection. #195

merged 2 commits into from
Jan 24, 2012

Conversation

Serabe
Copy link
Contributor

@Serabe Serabe commented Jan 24, 2012

Sorcery was using the inc method that was working. It got replaced by self.class.increment for mongo_mapper (increment instance method implementation in MongoMapper). Though, maybe changing the name of sorcery's method would be best.

Furthermore, it gives the count_attribute in said submodule a default value of 0, since it fails otherwise.

A workaround is needed since mongomapper method is increment too and it cannot be aliased there.
@NoamB
Copy link
Owner

NoamB commented Jan 24, 2012

Thanks - would be nice to have a test for this as well.

NoamB added a commit that referenced this pull request Jan 24, 2012
Solves problems between MongoMapper and brute_force_protection.
@NoamB NoamB merged commit 33b1b40 into NoamB:master Jan 24, 2012
@Serabe
Copy link
Contributor Author

Serabe commented Jan 24, 2012

Main problem testing the default value with mongo_mapper is that at the moment, default values are not applied until saving without monkey-patching. Not a clue how to work that out until they fix that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants