You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're testing out sorbet in our project, and CarrierWave is causing a couple of issues with the types that are generated. I've narrowed it down to this line:
Is there nothing more stable than object_id that could be used? Something that is stable across runs?
I've tried looking through the commit history and got to about 7 years ago. I'm not familiar with the internals of the project at all, but what is the benefit in using the object_id at all?
Edit: found this issue #793. It seems to be why the Uploader is named dynamically. I'm very for having some kind of dynamic name - that doesn't phase me. It'd just be great if it was stable across runs.
The text was updated successfully, but these errors were encountered:
Hey 👋
We're testing out sorbet in our project, and CarrierWave is causing a couple of issues with the types that are generated. I've narrowed it down to this line:
carrierwave/lib/carrierwave/mount.rb
Line 432 in d12a289
Is there nothing more stable than
object_id
that could be used? Something that is stable across runs?I've tried looking through the commit history and got to about 7 years ago. I'm not familiar with the internals of the project at all, but what is the benefit in using the
object_id
at all?Edit: found this issue #793. It seems to be why the
Uploader
is named dynamically. I'm very for having some kind of dynamic name - that doesn't phase me. It'd just be great if it was stable across runs.The text was updated successfully, but these errors were encountered: