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

Fixes towhat deprecation warnings #516

Merged
merged 1 commit into from
Dec 21, 2018

Conversation

NickLaMuro
Copy link
Member

This warning was added as part of: ManageIQ/manageiq#17545

There are other uses of towhat in the repo, but it is only a problem with MiqSchedule records being created by these factories that can be fixed here, and are the largest source of the warnings in the specs.

Links

This warning was added as part of:

ManageIQ/manageiq#17545

There are other uses of `towhat` in the repo but it is only a problem
with `miq_schedule` records being created by these factories that can be
fixed here.
@NickLaMuro
Copy link
Member Author

@miq-bot assign @bdunne

I think you were in charge of a decent amount of this effort, so assigning this to you.

@miq-bot
Copy link
Member

miq-bot commented Nov 28, 2018

Checked commit NickLaMuro@fca6f2d with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0
1 file checked, 0 offenses detected
Everything looks fine. ⭐

@bdunne bdunne merged commit dbf53bb into ManageIQ:master Dec 21, 2018
@bdunne bdunne added this to the Sprint 102 Ending Jan 7, 2019 milestone Dec 21, 2018
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