3 ms·
It might be a little of both. I did come across this change to keyword arguments[1] recently, but I'm not sure how impactful it is since I don't personally leve
by ilikepi 6y ago
It might be a little of both. I did come across this change to keyword arguments[1] recently, but I'm not sure how impactful it is since I don't personally leverage keyword arguments right now.
[1]: https://www.ruby-lang.org/en/news/2019/12/12/separation-of-positional-and-keyword-arguments-in-ruby-3-0/ https://www.ruby-lang.org/en/news/2019/12/12/separation-of-p...
- d3nj4l 6y agoIt sure does blow up your logs if you're using rails with 2.7.1.
- sosodev 6y agoHave you updated? Pretty sure all the warnings have been fixed now.
- ljm 6y agoProblem is if you're stuck on gems that aren't maintained any more. Seen a few with PRs containing fixes going stale. Can still switch to a fork, at least.
- jamie_ca 6y agoYeah, core rails the only warning I've seen is a single one in sprockets-rails (brand new app from last week).
- d3nj4l 6y agoCan't update at work, there's a few breaking changes :/