Handling Ruby 2.7 deprecations warnings
In Ruby 3.0, positional arguments and keyword arguments will be separated. For now ruby 2.7 brings deprecations warnings that notifies us that our code should be updated. In most cases adding or removing ** should fix the problem but the question is - how to find all occurrences in the code?If you have high test coverage it should be pretty easy - just run the specs and fix warnings one by one. What if you don't? Well, there is another solution.
Handling Ruby 2.7 deprecations warnings #ruby #rubydeveloper #rubyonrails