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.
For fields that contain non-string binary data (e.g. random tokens), base64 encode the value for display in list views and in forms, and base64 decode the value on save.
It's unlikely that you'll want such fields to actually have their value be visible and editable in kaffy. But all fields are visible and editable by default in kaffy, and we don't want a broken out-of-the-box experience for any field types. And, in case you do want to work with such fields, they should be visible in a legible / useful format, and they should be editable without the value getting corrupted on save.