Allow array fields on Patient to be empty #70
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.
Due to the combination of how
PatientUpdate
is structured and how JSON serialization works in Go, it has not been possible to completely remove emails and phones from a Patient record.This PR updates
PatientUpdate
so that ifEmails
orPhones
is non-nil, the field will be included in the JSON serialization output, even if the slice the field points to is empty. This allows consumers of the client to pass an empty array for these fields to Elation to allow them to be completely cleared.If
Emails
orPhones
is nil, then it will not be included in the JSON serialization output. This allows consumers of the client to change other fields on the Patient record without affecting emails or phones.For consistency, the
Consents
andInsurances
fields have been similarly modified to allow the fields in the Patient record to be cleared.