ArrayBuffers in attributes are not preserved #992
Draft
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.
When fetching a record with an ArrayBuffer attribute, it is sometimes preserved, and other times becomes an empty object.
If I had to guess, it might be deep cloning the object with
JSON.parse(JSON.stringify(record))
which doesn't preserve ArrayBuffers.Maybe there is a way I'm supposed to be handling this with serializers, but the fact that updating an unrelated attribute causes the issue seems like a bug for sure.
Maybe this test belongs further down, but I was having trouble following all the abstractions.