API: Accept single‑value integer ranges in IntegerRangeSerializer #1136

New Issue

MrUnknownDE · 2026-04-05T20:59:55+02:00

MrUnknownDE commented

2026-04-05 20:59:55 +02:00

Originally created by @pheus on 10/3/2025

NetBox version

v4.4.2

Feature type

Change to existing functionality

Proposed functionality

Extend the integer range serializer to accept single values in addition to the current 2‑value range format. Specifically, accept any of:

53
[53, 53]

This is most visible for VLANGroup VLAN ID ranges but applies to any field using the integer range serializer. The change is fully backward‑compatible: existing inputs (two‑element lists) continue to work, and output/representation remains unchanged.

Use case

When working with VLAN groups or other range fields, API clients often need to submit a single value. Allowing a bare integer avoids forcing clients to wrap a singleton as a two‑element range, reduces friction for simple operations, and matches user expectations from the UI (where singletons are common).

Changes required

Update IntegerRangeSerializer.to_internal_value() to normalize:
- int → (lo=val, hi=val)
- list|tuple of length 2 → (lo, hi)
Keep storage/representation semantics unchanged.

Database changes

None.

External dependencies

None.

Example:

[53, 53]

*Originally created by @pheus on 10/3/2025* ### NetBox version v4.4.2 ### Feature type Change to existing functionality ### Proposed functionality Extend the integer range serializer to accept **single values** in addition to the current 2‑value range format. Specifically, accept any of: - `53` - `[53, 53]` This is most visible for **VLANGroup** VLAN ID ranges but applies to any field using the integer range serializer. The change is fully backward‑compatible: existing inputs (two‑element lists) continue to work, and output/representation remains unchanged. ### Use case When working with VLAN groups or other range fields, API clients often need to submit a **single** value. Allowing a bare integer avoids forcing clients to wrap a singleton as a two‑element range, reduces friction for simple operations, and matches user expectations from the UI (where singletons are common). ### Changes required - Update `IntegerRangeSerializer.to_internal_value()` to normalize: - `int` → `(lo=val, hi=val)` - `list|tuple` of length 2 → `(lo, hi)` - Keep storage/representation semantics unchanged. ### Database changes None. ### External dependencies None. --- **Example:** ```json 53 ``` ```json [53, 53] ```

MrUnknownDE closed this issue

2026-04-05 20:59:55 +02:00

Sign in to join this conversation.

Branches Tags

main

21455-sql-indexes-audit

21357-register-model-actions

feature

20924-plugin-ui-components

21766-improve-test-coverage-for-sortable-table-columns

21157-export-template-public-models

21025-pre-render-config-contexts

21364-swagger

feature-ip-prefix-link

20911-dropdown-3

fix_module_substitution

21160-filterset

20911-dropdown-2

20044-elevation-stuck-lightmode

7604-filter-modifiers-v3

20660-script-load

19724-graphql

14884-script

19720-macaddress-interface-generic-relation

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

No Label type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/netbox#1136