Skip to content
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

Create SubstitutionCipher.js #1542

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Tharakadhanushka
Copy link

@Tharakadhanushka Tharakadhanushka commented Oct 15, 2023

SubstitutionCipher

Open in Gitpod know more

Describe your change:

  • Add an algorithm?
  • Fix a bug or typo in an existing algorithm?
  • Documentation change?

Checklist:

  • I have read CONTRIBUTING.md.
  • This pull request is all my own work -- I have not plagiarized.
  • I know that pull requests will not be merged if they fail the automated tests.
  • This PR only changes one algorithm file. To ease review, please open separate PRs for separate algorithms.
  • All new JavaScript files are placed inside an existing directory.
  • All filenames should use the UpperCamelCase (PascalCase) style. There should be no spaces in filenames.
    Example:UserProfile.js is allowed but userprofile.js,Userprofile.js,user-Profile.js,userProfile.js are not
  • All new algorithms have a URL in their comments that points to Wikipedia or another similar explanation.
  • If this pull request resolves one or more open issues then the commit message contains Fixes: #{$ISSUE_NO}.

SubstitutionCipher
@Tharakadhanushka

This comment was marked as duplicate.

Copy link
Collaborator

@appgurueu appgurueu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • Would need proper tests rather than an example with side effects.
  • Would need proper JSDoc comments.
  • This is pretty trivial. The only use case I would see is as a generalization of substitution chiffres; then it should be used to implement our existing substitution chiffres in terms of it though. That said, I think all of them aren't really interesting; all they do is really character-wise replacement with a substitution table. That's trivial.
  • To generalize properly, this shouldn't make arbitrary choices like uppercasing the plaintext.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants