I think the intention was to have another model
attr whose value is calculated on the frontend as opposed to the other fields which are exposed to the user directly via form input. This calculated field would factor into frontend validations so it needs to be accessible when creating local records on the frontend and needs to be serialized in the JSON when creating the entity on the backend.
For the time being I have updated the Serializer
serialize to include statements like
json.calculatedField = snapshot.record.calculatedField. Another option that I thought of would be to have the
getter in the model directly set a separate
attr field if that’s possible to bypass the need for customizing the serializer.