-
Notifications
You must be signed in to change notification settings - Fork 9
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
Remove the banner #649
Remove the banner #649
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #649 +/- ##
===========================================
- Coverage 91.05% 91.01% -0.04%
===========================================
Files 82 81 -1
Lines 2012 2004 -8
===========================================
- Hits 1832 1824 -8
Misses 180 180
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
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.
After some discussion and a bit of tears about the banner having 😭 to go I'm OK with this.
Still, could we actually move the banner and version information into the module docs?
Like, if people type ?COBREXA
, this (and the version information, etc.) could show up instead of the really completely useless README print-out.
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.
there was a COBREXA_VERSION
const defined in the banner, which was not internal and people (incl me) might have depended on it. I think it would be useful to have that preserved. Not sure if it can be reused within the module docstring though.
I still don't think this is nice ... |
The banner is totally unnecessary + a cobratoolbox left over, 🪓 it for v2.0.