Open
Conversation
Collaborator
|
@craig-rueda It seems like it's already possible to override default behavior by specifying the encryption engine when instantiating the class. @kvesteri I recommend closing this PR. Would you review and make a determination? |
Owner
|
I see the reason for this kind of functionality. However there are merge conflicts and this PR is missing unit tests. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Adds new class variable
default_enginetoStringEncryptedTypeto allow for overriding of default behavior. Currently,StringEncryptedType's ctor is hard-coded to utilize theAesEngineif no other engine is specified. This PR allows the default engine to be configured during app bootstrap.