You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When displaying the serialized representation of objects that have been created or deleted within a branch, omit any empty values (null, empty strings, empty arrays, etc.) from the output. For example, creating a site named "New Site" will show the following data in the "after" state of the change:
asns: []
comments:
custom_fields: {}
description:
facility:
group: None
latitude: None
longitude: None
name: New Site
physical_address:
region: None
shipping_address:
slug: new-site
status: active
tags: []
tenant: None
time_zone: None
Omitting empty values leaves only fields which contain meaningful data, namely the name and slug fields:
name: New Site
slug: new-site
This more closely resembles the behavior when modifying an existing object, where only the modified fields are shown.
Use case
This would reduce noise in the change log and simplify human review.
External dependencies
No response
The text was updated successfully, but these errors were encountered:
jeremystretch
changed the title
Omit "empty" values from change data for created & deleted objects
Omit "empty" values from displayed data for created & deleted objects
Sep 6, 2024
Plugin Version
v0.4.0
Proposed functionality
When displaying the serialized representation of objects that have been created or deleted within a branch, omit any empty values (null, empty strings, empty arrays, etc.) from the output. For example, creating a site named "New Site" will show the following data in the "after" state of the change:
Omitting empty values leaves only fields which contain meaningful data, namely the
name
andslug
fields:This more closely resembles the behavior when modifying an existing object, where only the modified fields are shown.
Use case
This would reduce noise in the change log and simplify human review.
External dependencies
No response
The text was updated successfully, but these errors were encountered: