Closed Flixt closed 2 years ago
Thanks @Flixt . This looks good to me. I think I'm okay not having a spec for this, at least for now.
I'd be okay having different Gemfiles for different ruby versions. We've already got a few different Gemfiles for the Rails versions. But honestly, it's probably time to stop supporting some of the 5.x versions. So we I'd be happy to cut back there.
With Ruby 3.1.0 we encountered the following error when enabling caching for collections.
Because the
Collection
does currently not splat theoptions
hash to keyword arguments. I could not come up with a good spec for this case, as the specs for theCollection
class mock the initialization of the plan itself. If you have a good idea on how to write a spec to avoid a regression I would be happy to add it.Additional question: What do you think about adding different Gemfiles for different ruby versions?