Cowsay#699
Conversation
doublevcodes
left a comment
There was a problem hiding this comment.
One pointer:
- What happens if the user enters a character that isn't supported? Add some sort of error for this.
Co-authored-by: Vivaan Verma <54081925+doublevcodes@users.noreply.github.com>
Co-authored-by: Vivaan Verma <54081925+doublevcodes@users.noreply.github.com>
ToxicKidz
left a comment
There was a problem hiding this comment.
Thanks for the PR! This looks pretty good to me, just one comment. Will test this later.
|
@doublevcodes resolved the errors |
janine9vn
left a comment
There was a problem hiding this comment.
Thanks for the PR! I have some minor recommendations to make this command a bit more robust to user input. Otherwise the command is fun and simple, so the rest of my review will focus on the overall contribution process and things to keep in mind for the future.
Commit messages!
Commit messages are hugely important in the review process and also looking back if we're curious why a command was coded a specific way. I'd recommend adding reasoning as to why you're add/removing/changing how something works.
For instance you have a commit that remove a for loop. I don't know why it was there originally or why it was removed. Having that information would be useful. It would also be useful for the commit where you removed trex from the documentation. I'm not sure why you removed it from the documentation although I imagine it has something to do with the fact that it's very likely to generate a response too large for discord to post.
Shivansh-007
left a comment
There was a problem hiding this comment.
Could you explain why you removed Trex from the documentation in commit 2a58874.
Co-authored-by: Shivansh-007 <shivansh-007@outlook.com>
|
@janine9vn ive resolved the changes you requested. |
Shivansh-007
left a comment
There was a problem hiding this comment.
Alright, few more nitpicks
|
@Kronifer what's your status for this PR? |
brad90four
left a comment
There was a problem hiding this comment.
A small question / suggestion for sending the user the character that raised the un-supported character error.
|
@Xithrius so sorry, I've been caught up in stuff but I'll be getting back to this shortly |
Co-authored-by: Shivansh-007 <shivansh-007@outlook.com>
Co-authored-by: Shivansh-007 <shivansh-007@outlook.com>
Co-authored-by: kgolawski <konrad.golawski@gmail.com>
Co-authored-by: brad90four <42116429+brad90four@users.noreply.github.com>
No problem. Remember to solve the conflicts in |
|
Alright, resolved that |
|
There seems to be some linting errors as well. Run |
|
@ToxicKidz please re-review |
Akarys42
left a comment
There was a problem hiding this comment.
Hey @Kronifer, first thanks a lot for all the time you are putting into this PR.
It has come to our attention that the package you added, cowsay, is licensed under GPL, which isn't compatible with the MIT license. We need to remove that package and replace it with something else.
One solution could be to copy the animals from an R clone which is licensed under MIT. We will let you solve this the way you want!
|
I've returned to school, so this may take longer than anticipated. I'll try and get it done soon! |
|
I'm putting this on pause until I have |
@Kronifer |
|
@Xithrius thanks for reminding me that this exists, I'll get on it soon |
Relevant Issues
Closes #667
Description
Added Cowsay command using the cowsay module
Reasoning
I used a pre-existing module, because a lot of the work had already really been done for me that way
Screenshots
Additional Details
ASCII art breaks on mobile for some reason
Did you:
pipenv lock?pipenv run lint)?