[8.x] Add types for casting encrypted strings to objects #34948
Merged
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.
Per the discussion in #34937, this is a fast-follow PR to add "types" or "formats" to specify additional casts for encrypted attributes.
This allows you to persist complex types like arrays, json, objects, or collections as encrypted values, while working with them naturally within your application.
Example:
I feel this rounds out this feature by covering the most common use cases. For anything more, a custom cast may be used.
Note: Since these are stored encrypted, you will most like want to use a
text
field for any attributes using these casts.