feat(api): Use JSONField for assigned_object serializer #248
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.
Pull Request
Related Issue
Fixes: #247 [Housekeeping]: Use JSONField for assigned_object serializer
New Behavior
DictField
withJSONField
forassigned_object
to align with NetBox best practices.assigned_object
returnsNone
without errors.display
tobrief_fields
forACLInterfaceAssignment
and improves its string representation.Contrast to Current Behavior
JSONField
, which is the preferred approach in NetBox core.display
attribute toACLInterfaceAssignment
, ensuring consistency with other NetBox API objects.Discussion: Benefits and Drawbacks
Changes to the Documentation
Proposed Release Note Entry
Double Check
or in a linked issue.
dev
branch.