-
Notifications
You must be signed in to change notification settings - Fork 24
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
ENH: Add feedback to result saving #110
Conversation
👍, I like the current wording. Do you think it'd be helpful to distinguish between artifacts and visualizations? i.e. What do you think about echoing using green text? That way it's easy to spot, plus it's a "successful" operation. Do you think this should always echo (like it is now)? Or should
I like the current behavior because it'll be relative if the user provided a relative path, and absolute otherwise. @thermokarst @ebolyen, interested in your thoughts. |
I like differentiating between viz and artifact in the message, also formatting the text green sounds great. I also like the current behavior, echoing whatever the user provided as far as path. Maybe |
Thanks @jairideout and @thermokarst, here's the updated output: |
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.
This looks so fancy @jakereps!
👍 , thanks @jakereps ! |
ENH: Adds qiime.plugin.plugin_init to initialize plugin package from …
Resolves #98
Thoughts on verbiage?
Saved to:
Written to:
<filepath only>
. Extend the filepath beyond the relative path that is returned by.save()
?