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

Give Slim Select another chance #11781

New Issue
Closed
opened 2025-12-29 21:49:46 +01:00 by adam · 2 comments
adam commented 2025-12-29 21:49:46 +01:00
Owner
Copy Link

Originally created by @brianvoe on GitHub (Oct 26, 2025).

NetBox version

N/A

Feature type

Change to existing functionality

Proposed functionality

I am the developer of Slim Select and noticed an old issue where you moved away to tom select. https://github.com/netbox-community/netbox/issues/14917

I just did a big version release and if you ever wanna come back I would be more than happy to help.
https://github.com/brianvoe/slim-select/releases/tag/v3.0.0

Use case

I might be biased but I think slim select is the best, if you dont think so let me know and ill see what i can do.

Database changes

No response

External dependencies

No response

Originally created by @brianvoe on GitHub (Oct 26, 2025). ### NetBox version N/A ### Feature type Change to existing functionality ### Proposed functionality I am the developer of Slim Select and noticed an old issue where you moved away to tom select. https://github.com/netbox-community/netbox/issues/14917 I just did a big version release and if you ever wanna come back I would be more than happy to help. https://github.com/brianvoe/slim-select/releases/tag/v3.0.0 ### Use case I might be biased but I think slim select is the best, if you dont think so let me know and ill see what i can do. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurenetbox labels 2025-12-29 21:49:46 +01:00
adam closed this issue 2025-12-29 21:49:47 +01:00
adam commented 2025-12-29 21:49:47 +01:00
Author
Owner
Copy Link

@jnovinger commented on GitHub (Oct 28, 2025):

Thanks for the heads up, @brianvoe. We moved from slim-select to tom-select after evaluating alternatives in early 2024, as you noted. tom-select has been working well for our needs since then and given the amount of other work we have at the moment, we do not foresee making a switch in the near future.

@jnovinger commented on GitHub (Oct 28, 2025): Thanks for the heads up, @brianvoe. We moved from slim-select to tom-select after evaluating alternatives in early 2024, as you noted. tom-select has been working well for our needs since then and given the amount of other work we have at the moment, we do not foresee making a switch in the near future.
adam commented 2025-12-29 21:49:47 +01:00
Author
Owner
Copy Link

@brianvoe commented on GitHub (Oct 28, 2025):

understandable. good luck with everything.

@brianvoe commented on GitHub (Oct 28, 2025): understandable. good luck with everything.
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 netbox type: feature
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#11781
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?