starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Replace slim-select with tom-select #9142

New Issue
Closed
opened 2025-12-29 20:46:11 +01:00 by adam · 1 comment
adam commented 2025-12-29 20:46:11 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Jan 24, 2024).

Originally assigned to: @jeremystretch on GitHub.

Proposed Changes

We currently employ the slim-select library to facilitate dynamic, API-backed dropdown widgets in the user interface. We are currently using v1.27, which is far out of date. This issue proposes replacing slim-select with the alternative tom-select library.

If accepted, this proposal would negate #14734.

Justification

There are a few reasons I'm leaning toward tom-select:

  1. The Tabler framework ships with native styling for tom-select inputs
  2. Tom-select seems to provide more thorough documentation
  3. Initial experimentation with tom-select has been very promising, and it feels like it would easily support #13283
  4. Upgrading slim-select to v2.8 would essentially require rewriting the current implementation (and there's apparently no migration guide provided)
Originally created by @jeremystretch on GitHub (Jan 24, 2024). Originally assigned to: @jeremystretch on GitHub. ### Proposed Changes We currently employ the [slim-select](https://slimselectjs.com/) library to facilitate dynamic, API-backed dropdown widgets in the user interface. We are currently using v1.27, which is far out of date. This issue proposes replacing slim-select with the alternative [tom-select](https://tom-select.js.org/) library. If accepted, this proposal would negate #14734. ### Justification There are a few reasons I'm leaning toward tom-select: 1. The Tabler framework ships with native styling for tom-select inputs 2. Tom-select seems to provide more thorough documentation 3. Initial experimentation with tom-select has been very promising, and it feels like it would easily support #13283 4. Upgrading slim-select to v2.8 would essentially require rewriting the current implementation (and there's apparently no migration guide provided)
adam added the status: acceptedtype: housekeeping labels 2025-12-29 20:46:11 +01:00
adam closed this issue 2025-12-29 20:46:11 +01:00
adam commented 2025-12-29 20:46:12 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 25, 2024):

We discussed this in today's maintainers' meeting and decided to move ahead with tom-select.

@jeremystretch commented on GitHub (Jan 25, 2024): We discussed this in today's maintainers' meeting and decided to move ahead with tom-select.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: accepted type: housekeeping
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#9142
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?