Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deletion of objects from child tables should leverage HTMX (like the parent object) #9860

Open
jeremystretch opened this issue Jul 27, 2022 · 4 comments
Labels
complexity: high Expected to require a large amont of time and effort to implement relative to other tasks netbox status: blocked Another issue or external requirement is preventing implementation topic: UI/UX User interface or user experience related work type: feature Introduction of new functionality to the application

Comments

@jeremystretch
Copy link
Member

NetBox version

v3.2.7

Feature type

Change to existing functionality

Proposed functionality

When viewing a list of child objects under a parent object (for example, when viewing the list of interfaces under a device), deleting any of the objects within the table should utilize an HTMX-powered modal (rather than taking the user to a new URL), just as deleting the parent object does.

Use case

Avoids a full page load to display the deletion confirmation dialog.

Database changes

No response

External dependencies

No response

@jeremystretch jeremystretch added type: feature Introduction of new functionality to the application status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation labels Jul 27, 2022
@barnebyte-timewarp
Copy link
Contributor

I think i have a simple solution for this, you can assign it to me

@github-actions
Copy link
Contributor

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. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions github-actions bot added the pending closure Requires immediate attention to avoid being closed for inactivity label Oct 12, 2022
@github-actions
Copy link
Contributor

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 12, 2022
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation pending closure Requires immediate attention to avoid being closed for inactivity labels Nov 14, 2022
@jeremystretch jeremystretch self-assigned this Nov 14, 2022
@jeremystretch jeremystretch reopened this Nov 14, 2022
@jeremystretch jeremystretch removed their assignment Dec 27, 2023
@jeremystretch jeremystretch added status: blocked Another issue or external requirement is preventing implementation topic: UI/UX User interface or user experience related work labels Dec 27, 2023
@jeremystretch
Copy link
Member Author

Blocked by #12128

@jeremystretch jeremystretch added complexity: high Expected to require a large amont of time and effort to implement relative to other tasks and removed status: accepted This issue has been accepted for implementation labels May 22, 2024
@jeremystretch jeremystretch added the netbox label Nov 1, 2024 — with Linear
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complexity: high Expected to require a large amont of time and effort to implement relative to other tasks netbox status: blocked Another issue or external requirement is preventing implementation topic: UI/UX User interface or user experience related work type: feature Introduction of new functionality to the application
Projects
None yet
Development

No branches or pull requests

2 participants