-
Notifications
You must be signed in to change notification settings - Fork 26
Developersdevelopersdevelopers #43
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
Developersdevelopersdevelopers #43
Conversation
mckern
commented
Mar 1, 2017
Formatting is slightly more idiomatic now.
I think Travis is going to throw up on Ruby 2.3 and/or 2.4. The problem isn't the library, it's the tests. Investigating when I can get a straight answer out of Travis. |
As per https://opensource.org/licenses/alphabetical, the name should be Apache-2.0, not Apache.
Pessimistic versioning means that Faraday 0.11.0 will be installed if the constraint is "~> 0.9", and that will break spec tests due to newer restrictions in Faraday around how HTTP requests are handled by rspec. We don't want to break tests.
Instead of having a hardcoded version identifier in multiple locations, we can leverage the Classname::VERSION pattern to have a single canonical version number that everything can reference programmatically.
@@ -16,7 +16,7 @@ class Vmfloaty | |||
include Commander::Methods | |||
|
|||
def run | |||
program :version, Version.get | |||
program :version, Vmfloaty::VERSION |
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.
Cool, haven't tried this yet but I've tried to get this to work this way for a couple of times now and it never seems to behave correctly. 👍
I have a Rubocop PR pending too. |
Ruby 2.0 is dead, but 2.1 is not. Of note is that Ruby 2.1 *will* be unsupported soon, but it's definitely not dead yet.
LOOKS GOOD 👍 |