Feature/weos 1399 - Added hashing functionality #172
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Added scenario for bcrypt * Added scenario for sha256 * Added scenario for sha3-256 * Added scenario for sha3-512 * Added scenario for base64 * Fixed issue with default api.yaml
* Improve the spacing
- Added functionality for bcrypt, base64, sha256, sha3_256, sha3_512 - Added tests for all above mentioned hashed
# Conflicts: # features/define-content-type-oas.feature
- Updated feature file
- Updated feature file
- Added update functionality and unit tests
- Added an hash update e2e test
Weos 1399 -As a developer I should be able to indicate a field is hashed or encoded
Aidan-E
approved these changes
May 4, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
What is the current behavior? (You can also link to an open issue here)
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Other information: