-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Extend the Digest::UUID module with the clean method #81
Conversation
We can ignore the Hakiri warning, it's a bug on their end. |
I know you're just moving code from a different repo, but when I put on my non-ManageIQ more_core_extensions hat 🎩 I wonder if this should instead be one or more of:
@Fryguy Any thoughts? |
I don't like the string patches, because to_uuid I would expect some kind of UUID object out the other side, not for it to be cleaned. Same with .from_string. .format is not bad, but I think .clean is clearer. |
Checked commits https://github.com/djberg96/more_core_extensions/compare/3d731e860bbc40a42868f5e65f743b62515b06b3~...d252b90d5dd2e491616215de754a3f9e45eac8f0 with ruby 2.5.7, rubocop 0.69.0, haml-lint 0.28.0, and yamllint lib/more_core_extensions/core_ext/digest/uuid.rb
|
@Fryguy Look ok now? |
@Fryguy Any concerns? |
Since Rails 5.1+ gives us the Digest::UUID class, let's extend it with the
clean
method here. The eventual goal is to update the core Hardware class with this method, and remove miq-uuid from gems-pending.