What kinds of things are you seeing? I believe this was done pre 6.1.0, but the Ruby version shouldn’t matter. If starting a new app, I would probably target Ruby 3.X. However, if it were something that was a shared library, I would target a lower version but also test compatibility with 3.0.
This episode was on Ruby 2.7.2 and Rails 6.1.0. It's probably worth noting that I do have a .railsrc file which contains.
--skip-spring
--skip-coffee
This episode was also based on the version of hotwire-rails 0.1.0 and turbo-rails 0.5.0 at the time. They are moving fairly quickly with their development. What differences are you finding?
Thanks ☒ . I'm still researching how I would handle it as the current solutions that I've come up with aren't up to my satisfaction yet. I have some ideas, but not fully ready to share. The ideas that I'm bouncing around is a background job which periodically handles the orphan records. However, this imposes additional infrastructure which may not already be in place. It could also be expensive in cases where Active Storage is heavily used. I think that a better route would be to have a background job which is triggered to be performed at a later time which can then check later if the record is orphaned or not. However, this also has its own drawbacks because there could be a case where a small queue server could get overwhelmed with requests and essentially lost jobs.
