Open andrewpbrett opened 3 years ago
I think we can probably delay this for now. In the future when we bump to higher versions of Rails or Ruby, I imagine we'll find at some point that the current version of the gem has some incompatibilities. We'll be forced to play around with bumping it and upgrading it at that point, but I'm not sure there's strong need to address it before then...
What we should change and why (this is tech debt)
We need to do some work to un-break the build for an upgrade to cancancan 2.0, to start, and then to catch up to the current version.
Context
https://github.com/openfoodfoundation/openfoodnetwork/pull/6639
Impact and timeline