-
Notifications
You must be signed in to change notification settings - Fork 270
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
Caesar cipher [Fixed #40] [Fixed #44] #57
Conversation
Hey is there any problem with this? |
Sorry for late reply @Omkaragrawal . |
Hey I have repaired all the expect().toBe() according to @fcosueza 's comments. Now is it OK? |
Please look into this @TheSTL |
@@ -0,0 +1,46 @@ | |||
/** |
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.
Creating a completely new file is not acceptable. I am marking this PR as Invalid and closing it. However, we can go ahead and keep your Unit Tests somehow
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.
Hey give me sometime as I have university exams going on, I'll try to update the old code itself asap.
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.
But I am not clear as to why a new code (that solves previous issues and have some new features) is not acceptable. Would you not consider this?
I have created my own Caesar Cipher file, along with tests. I Fixed #40 also Fixed #44 .