-
Notifications
You must be signed in to change notification settings - Fork 8
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
Fix deprecation warnings #15
Fix deprecation warnings #15
Conversation
dry-types 0.12.0 deprecated Types::Array#member and introduced a replacement Types::Array#of in the same release [1]. Sigh. This means that for dry-types <0.12, you must use Types::Array#member because #of doesn't exist, but for dry-types >=0.12, you must use Types::Array#of because #member emits a noisy deprecation warning. This commit is a quick fix: it changes the gemspec to require >= 0.12, and uses #of. [1]: https://github.com/dry-rb/dry-types/blob/master/CHANGELOG.md#v0120-2017-09-15
BTW I haven't actually tested this - I couldn't see any development or hacking docs to indicate how to run the tests |
I don't see anything in my PR that caused the build to fail 😕 the rubocop issues were there already |
I've also just discovered that these deprecation warnings break |
Remove the Ruby 2.1 test from |
@randomvariable if we remove it from |
Yup, and the README.md. We'll bump to 1.0.0 after this I think. |
I used 2.3.1 because I happen to have it installed locally :)
rubocop fails massively for me locally, i feel like i'm missing some definitions somewhere. pushed an update as discussed anyway. |
dry-types 0.12.0 deprecated Types::Array#member and introduced a
replacement Types::Array#of in the same release. Sigh.
This means that for dry-types <0.12, you must use Types::Array#member
because #of doesn't exist, but for dry-types >=0.12, you must use
Types::Array#of because #member emits a noisy deprecation warning.
This commit is a quick fix: it changes the gemspec to require >= 0.12,
and uses #of.