-
Notifications
You must be signed in to change notification settings - Fork 44
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
🌺 Quality of life improvements #49
Conversation
@gratcliff You should take a look at this to make sure I didn't lose anything you added in the versions additions. |
Absolutely! In the processes of looking as we speak. Some of that |
I noticed when importing a spec file with the CLI tool that the command is different: It doesn't indicate that the Swagger file needs to come after "swagger" which might be confusing to new users. It would be clearer if it looked something like this: I don't know what the reason was for changing it but maybe this is something to consider? |
@amyshi188 How about this instead:
I kind of want to keep |
@amyshi188 We actually changed it so you don't need the path to the file anymore! If you don't provide one it will automatically try to find one, and if it can't then we ask the user to enter the path. So for new users it's probably better to not include the path at all! |
I'm good to keep the usage for the swagger command as I talked offline with @gratcliff and I've accidentally removed a heap of argument support on the new versions commands, so I'm working on resurrecting those. |
@gratcliff @mjcuva Pushed up a handful of fixes for the
|
I agree with you that the table is cleaner, but it's pruning some key information in regards to pulling specific versions: |
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.
Looks great overall. Clean code is previously mentioned. In regards to version outputs, it may be beneficial to dump JSON. Either A) for mocking or B) to pipe into a bash script for programmatic usage. Otherwise, there should be differing information between rdme versions
and rdme versions --version=VERSION
(select v entire object dump, respectively). If you'd like to keep the table, maybe it makes sense to add a pretty
flag?
@gratcliff That's fair, but I was thinking that since this is a CLI wrapper around the API, that everything should be "pretty" by default. Maybe we can add a I'll go back and work in the missing data for the single version that I'm not currently surfacing in the prettified version though. |
Works for me! If we do can you update the |
@gratcliff Took another pass on
Since we don't have an API endpoint to pull information from |
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.
Jon this looks fantastic! Minor request below
rdme as it exists has a horde of usability issues:
There's got to be a better way!
Improvements
rdme <command> --help
andrdme help <command>
rdme help versions
, you'll see a related commands list of every other versions-related command available.rdme help
screen because everyone needs more Owlbert.In action