-
-
Notifications
You must be signed in to change notification settings - Fork 554
crypto-square: apply lowerCamelCase policy #1168
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
Conversation
"cases": [ | ||
{ | ||
"description": "empty plaintext results in an empty ciphertext", | ||
"property": "ciphertext", | ||
"description": "empty plainText results in an empty cipherText", |
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.
I assume you deliberately chose to use the property names, but I think it would maybe be better to use plain text
and cipher text
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.
fixed descriptions to not use property names in text.
3e1a63f
to
3b88936
Compare
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.
so, do you mind if I ask for these to remain ciphertext and plaintext?
https://en.wikipedia.org/wiki/Plain_text is significantly different from https://en.wikipedia.org/wiki/Plaintext , and I believe plaintext is more applicable to the situation at hand (cryptography).
https://en.wikipedia.org/wiki/Cipher_text redirects to https://en.wikipedia.org/wiki/Ciphertext
Not at all @petertseng. Thanks for the feedback. |
3b88936
to
2982fbd
Compare
@petertseng you were only referring to their use in the descriptions right? |
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.
I'll show an example for one test case; consider me to say the same for all of them.
"cases": [ | ||
{ | ||
"description": "empty plaintext results in an empty ciphertext", | ||
"property": "ciphertext", | ||
"property": "cipherText", |
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.
I think ciphertext is a better property than cipherText, so I would revert this change.
"input": { | ||
"plaintext": "" | ||
"plainText": "" |
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.
I think plaintext is a better input key than plainText, so I would revert this change.
@@ -1,60 +1,60 @@ | |||
{ | |||
"exercise": "crypto-square", | |||
"version": "3.2.0", | |||
"version": "3.2.1", | |||
"cases": [ | |||
{ | |||
"description": "empty plaintext results in an empty ciphertext", |
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.
I think this is good. I think "plaintext" and "ciphertext" are better in descriptions than "plain text" and "cipher text"
Closing this PR. Citing https://en.wikipedia.org/wiki/Plaintext. For this exercise "plaintext" and "ciphertext" are treated as single words. |
per #987