-
Notifications
You must be signed in to change notification settings - Fork 53
Start testing & supporting MongoDB #410
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
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #410 +/- ##
==========================================
+ Coverage 90.43% 90.69% +0.25%
==========================================
Files 14 14
Lines 847 849 +2
==========================================
+ Hits 766 770 +4
+ Misses 81 79 -2 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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.
I would love to have a way to not have more 1 billion of if/elses in theses files 😅. Let's make it first and ensure everything is very well tested, so we can improve the gem once and for all 🫡
Absolutely! On principle I'm starting all changes from the tests first, afterward I'm planning to use composition for storage backends, i. e. when Also I can remove at least one of the |
No special configuration here, a basic copy/paste of the example in https://github.com/marketplace/actions/mongodb-in-github-actions
The bugfix on Mongoid is not released yet, but that should not matter since there is no real reason to turn this back to after_destroy_commit. The behavior is equivalent.
Codecov is happy, and so is rubocop. The after_commit callback is fixed. I'll go ahead with the rest of the work on Mongoid on another PR if you have no notes on this one as a foundation @brunoocasali |
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.
LGTM
bors merge |
1 similar comment
bors merge |
@curquiza can you take a look and see what's happening with Bors? |
Pull Request
Related issue
Begins to fix #175