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

Allow plugins to inject sub-tabs on object detail views #9072

Closed
jeremystretch opened this issue Apr 7, 2022 · 3 comments
Closed

Allow plugins to inject sub-tabs on object detail views #9072

jeremystretch opened this issue Apr 7, 2022 · 3 comments
Assignees
Labels
status: accepted This issue has been accepted for implementation topic: plugins Relates to the plugins framework type: feature Introduction of new functionality to the application
Milestone

Comments

@jeremystretch
Copy link
Member

NetBox version

v3.2.0

Feature type

New functionality

Proposed functionality

Object detail views typically have several tabs: the primary object details, the object change log, and the journal, for example. Some objects have additional tabs. This proposal (borne from discussion in WG8333) seeks to allow plugins to inject arbitrary additional tabs for particular objects.

The exact implementation is open for discussion, but it seems reasonable to assume that a plugin could register one or more (name, view) tuples to specific NetBox models identified by their app label and model name.

One likely blocker here is that we'll need to come up with a way to programmatically declare sub-tabs under a view, but this would serve the existing changelog & journal views as well.

Use case

Provides a greater degree of integration with core NetBox models and more convenient navigation for the user.

Database changes

No response

External dependencies

No response

@jeremystretch jeremystretch added type: feature Introduction of new functionality to the application status: under review Further discussion is needed to determine this issue's scope and/or implementation topic: plugins Relates to the plugins framework labels Apr 7, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Jun 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 github-actions bot added the pending closure Requires immediate attention to avoid being closed for inactivity label Jun 7, 2022
@jeremystretch jeremystretch added needs milestone Awaiting prioritization for inclusion with a future NetBox release and removed status: under review Further discussion is needed to determine this issue's scope and/or implementation pending closure Requires immediate attention to avoid being closed for inactivity labels Jun 9, 2022
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed needs milestone Awaiting prioritization for inclusion with a future NetBox release labels Jul 27, 2022
@jeremystretch jeremystretch added this to the v3.4 milestone Jul 27, 2022
@jeremystretch jeremystretch self-assigned this Sep 27, 2022
jeremystretch added a commit that referenced this issue Oct 7, 2022
jeremystretch added a commit that referenced this issue Oct 7, 2022
@kkthxbye-code
Copy link
Contributor

Such a good addition to the plugin API!

@jeremystretch
Copy link
Member Author

Not only that, it also allows us to clean up quite a bit of cruft and redundancy internally!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation topic: plugins Relates to the plugins framework type: feature Introduction of new functionality to the application
Projects
None yet
Development

No branches or pull requests

2 participants