-
-
Notifications
You must be signed in to change notification settings - Fork 200
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
fix strict_loading_by_default in BaseRecord #1475
Conversation
Thanks for the fix! If I run tests with this config value, I'm getting a few other violations and I'm wondering if those need to be handled as well. Some are test-only but a few happen in library code around batches. Edit: Those all seem to be batch-related so I find it likely you just don't use those. |
@Earlopain I'll take a look and try to fix them 👍🏼 |
Looks like you can overwrite this per-class with In my eyes, you can leave that for a followup issue/pr if you don't want to bother with that. This one right now fixes what you ran into. |
@Earlopain Just now I disabled strict loading for all GoodJob models. As you you said this is the way to go. |
What timing. Yeah, I think this good like that. |
Maybe you can keep your first commit as well? Seems like a good enough improvement to make regardless |
@Earlopain will this be included in the next version? |
Thank you both 🙇 I've been offline the past few days so I'll get this merged and released in the next version (very soon!) |
This has been released: https://github.com/bensheldon/good_job/releases/tag/v4.2.1 |
Include executions association to prevent
ActiveRecord::StrictLoadingViolationError
Fixes #1474