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

Deprecate any uses of class_name with Class objects in put_or_update #18831

Merged
merged 1 commit into from
May 31, 2019

Conversation

jrafanie
Copy link
Member

Rails 5.1 dropped support for query values of type Class, and we should
have fixed most of them with #18827 and #18829, but since detecting
callers to put_or_update that do this could be difficult, we can still
support this by "fixing" it so rails 5.1 doesn't raise an exception,
and give us time to fix the caller.

Rails 5.1 dropped support for query values of type Class, and we should
have fixed most of them with ManageIQ#18827 and ManageIQ#18829, but since detecting
callers to put_or_update that do this could be difficult, we can still
support this by "fixing" it so rails 5.1 doesn't raise an exception,
and give us time to fix the caller.
@jrafanie jrafanie requested a review from bdunne May 31, 2019 15:47
@miq-bot
Copy link
Member

miq-bot commented May 31, 2019

Checked commit jrafanie@af5b7fa with ruby 2.3.3, rubocop 0.69.0, haml-lint 0.20.0, and yamllint 1.10.0
2 files checked, 0 offenses detected
Everything looks fine. 🏆

@bdunne bdunne merged commit 1535bd9 into ManageIQ:master May 31, 2019
@bdunne bdunne self-assigned this May 31, 2019
@bdunne bdunne added this to the Sprint 113 Ending Jun 10, 2019 milestone May 31, 2019
@jrafanie jrafanie deleted the deprecate_class_class_name branch May 31, 2019 16:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants