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.
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
feat: Add
@encrypted
enhancer #1922base: dev
Are you sure you want to change the base?
feat: Add
@encrypted
enhancer #1922Changes from 10 commits
23a06cc
7784099
f8ee204
6bff7f4
b86e814
e0789b7
688d92d
aedbd93
8752f06
83c242c
d9b95ef
2ea8bd2
78046b3
9d16be0
29b7d15
a7169ef
acb2ee2
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Is it the same as
const bytes = encoder.encode(atob(data))
?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'm not sure why, but doing
const bytes = encoder.encode(atob(data))
doesn't have any type errors, but throws an error onbuild
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 supposed we don't want to add the
encrypted
enhancement by default?Doing so, would require the user to specify encryption options during setup, which would cause a breaking change for current users.
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.
Shall we validate the shape of
options.encryption
? Here or inside theEncryptedHandler
constructor.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 feel like validating inside of the handler constructor makes better sense, and its together with the rest of the
encrypted
logicThere 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.
If decryption fails, should we return the original cipher text? I'm thinking this will allow easier adoption: the
@encrypted
attribute can be added and deployed and then a background script is run to migrate the existing plain-text data.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.
Shall we add a nullish check to
data
here?