-
Notifications
You must be signed in to change notification settings - Fork 182
bigdecimal 2 support #370
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bigdecimal 2 support #370
Conversation
BigDecimal 2.0 no longer supports `.new`. looks like this gem uses both `BigDecimal(x)` and `BigDecimal.new(x)` - mind if we upgrade these last few calls?
@dpep I suppose, you are suggesting these changes because of error on upgrading to ruby BTW ruby |
@sharshenov Thanks for jumping in to help! I pulled in a gem that depended on BigDecimal v2, which caused the trouble. Similarly, Ruby 2.7 ships with that version, which looks like it breaks activesupport 3 and 4 also. I updated the travis matrix per your request Details: https://github.com/ruby/bigdecimal#which-version-should-you-select I'll look into the create/update deprecation warning and may follow up in a separate PR if that's ok? Anything else you want to see here? |
Ruby 2.7 deprecates automatic conversion from a hash to keyword arguments https://blog.saeloun.com/2019/10/07/ruby-2-7-keyword-arguments-redesign.html fixing those up, plus one more I noticed in the logs from JsonApiClient#370 (comment) https://travis-ci.org/github/JsonApiClient/json_api_client/jobs/722402404 thanks @sharshenov
@sharshenov fixed those warning in #371 |
Huge thanks! I was investigating the BigDecimal problem with ruby 2.7 and was going to push my fix, but then I saw your PR 🥇 |
@gaorlov : mind taking a look at this change as well? any changes you'd like to see here? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your contribution, @dpep!
We usually bump the version and changelog in master. Next time!
Thanks again!
@dpep @sharshenov |
BigDecimal 2.0 no longer supports
.new
. looks like json_api_client uses bothBigDecimal(x)
andBigDecimal.new(x)
- mind if we upgrade these last few calls?