Skip to content

Conversation

Omkaragrawal
Copy link

I have created my own Caesar Cipher file, along with tests. I Fixed #40 also Fixed #44 .

@Omkaragrawal
Copy link
Author

Hey is there any problem with this?

@TheSTL
Copy link
Member

TheSTL commented Oct 10, 2019

Sorry for late reply @Omkaragrawal .
You should debug the code. Don't create your own new algo file.

@Omkaragrawal
Copy link
Author

Hey I have repaired all the expect().toBe() according to @fcosueza 's comments. Now is it OK?

@ashokdey
Copy link
Member

Please look into this @TheSTL

@@ -0,0 +1,46 @@
/**
Copy link
Member

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

Copy link
Author

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.

Copy link
Author

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?

@ashokdey ashokdey added changes-requested invalid This doesn't seem right labels Oct 31, 2019
@ashokdey ashokdey closed this Jan 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changes-requested invalid This doesn't seem right
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Caesar cipher Add Unit Test for - Caeser Cipher
5 participants