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

Employ HTMX to render emedded tables #5848

New Issue
Closed
opened 2025-12-29 19:33:27 +01:00 by adam · 4 comments
adam commented 2025-12-29 19:33:27 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Dec 29, 2021).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.1.2

Feature type

New functionality

Proposed functionality

Leverage HTMX to allow ordering and paginating tables of related objects embedded within an object view. For example, when viewing images attached to a device (originally raised in #7003). We should be able to leverage the existing functionality on ObjectListView to support this.

Use case

Provides a more responsive and efficient UX.

Database changes

No response

External dependencies

No response

Originally created by @jeremystretch on GitHub (Dec 29, 2021). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.1.2 ### Feature type New functionality ### Proposed functionality Leverage HTMX to allow ordering and paginating tables of related objects embedded within an object view. For example, when viewing images attached to a device (originally raised in #7003). We should be able to leverage the existing functionality on ObjectListView to support this. ### Use case Provides a more responsive and efficient UX. ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: feature labels 2025-12-29 19:33:27 +01:00
adam closed this issue 2025-12-29 19:33:28 +01:00
adam commented 2025-12-29 19:33:28 +01:00
Author
Owner
Copy Link

@sdktr commented on GitHub (Jan 5, 2022):

While great for the user experience, i'm worried that all the effort into htmx will later on be a reason to not employ an api-based gui because of all the duplicate effort?

The api based gui might not be a goal in itself, but will probably not become one anytime soonish if further investments in the bootstrap framework are continued?

@sdktr commented on GitHub (Jan 5, 2022): While great for the user experience, i'm worried that all the effort into htmx will later on be a reason to not employ an api-based gui because of all the duplicate effort? The api based gui might not be a goal in itself, but will probably not become one anytime soonish if further investments in the bootstrap framework are continued?
adam commented 2025-12-29 19:33:28 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 5, 2022):

What's nice about HTMX is that it can be implemented opportunistically with very little effort relative to a complete API-driven framework like React or Vue. In fact, we may find that its strategic deployment obviates the need for such a framework entirely. In any case, there are myriad other factors which have prevented work on implementing a new UI framework over the past several years, not the least of which is an absence of any interested volunteers.

@jeremystretch commented on GitHub (Jan 5, 2022): What's nice about HTMX is that it can be implemented opportunistically with very little effort relative to a complete API-driven framework like React or Vue. In fact, we may find that its strategic deployment obviates the need for such a framework entirely. In any case, there are myriad other factors which have prevented work on implementing a new UI framework over the past several years, not the least of which is an absence of any interested volunteers.
adam commented 2025-12-29 19:33:29 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Mar 7, 2022):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Mar 7, 2022): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:33:29 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 13, 2023):

I'm making great progress with this. Still have a number of embedded table to update, but that's mostly boilerplate work.

@jeremystretch commented on GitHub (Jan 13, 2023): I'm making great progress with this. Still have a number of embedded table to update, but that's mostly boilerplate work.
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: 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#5848
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?