You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Gemspec/RequiredRubyVersion cop checks that spec.required_ruby_version= (if present) corresponds to TargetRubyVersion.
That's good.
I'd like a more basic check: that required_ruby_version is there at all. I believe that it should be an accepted community standard to have it; there is no valid reason not to have a required_ruby_version specified that I can think of.
I opened an rfc about that, but it would probably take time before this is accepted / implemented / released and mostly updated... A Rubocop might make things faster.
In case there is a .travis.yml file, it would be nice to check it correponds too.
How does a cop making required_ruby_version mandatory sound?
If that's a go, should it be a different cop?
What about .travis.yml check?
The text was updated successfully, but these errors were encountered:
The
Gemspec/RequiredRubyVersion
cop checks thatspec.required_ruby_version=
(if present) corresponds toTargetRubyVersion
.That's good.
I'd like a more basic check: that
required_ruby_version
is there at all. I believe that it should be an accepted community standard to have it; there is no valid reason not to have arequired_ruby_version
specified that I can think of.I opened an rfc about that, but it would probably take time before this is accepted / implemented / released and mostly updated... A Rubocop might make things faster.
In case there is a
.travis.yml
file, it would be nice to check it correponds too.How does a cop making
required_ruby_version
mandatory sound?If that's a go, should it be a different cop?
What about
.travis.yml
check?The text was updated successfully, but these errors were encountered: