-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Add direct create links to navigation menu for cables and wireless links #12127
Comments
I'll take this one |
@decoupca this is going to be more involved than it likely appears: The cable creation view and form need to be rewritten to accommodate dynamic changes using HTMX. |
@jeremystretch Do you have an example of a similar view/form I can reference? |
@decoupca I'm afraid not. This will need to be entirely original work. Do you still want to take it? |
Thanks -- I don't think I can handle this in a timely manner. I'll leave this to more experienced folks. |
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. |
Rescuing from auto-closure. Let's revisit in light of #12128 now being completed, perhaps that work lightens the lift somewhat? |
NetBox version
v3.5-beta1
Feature type
New functionality
Proposed functionality
Add "create" links to the navigation menu for cables and wireless links. This was previously not possible because rendering the creation form required some contextual information about the terminations, however recent improvements (#11625, #10054) have unlocked this ability.
Use case
Provides a more convenient path to creating these objects.
Database changes
No response
External dependencies
No response
The text was updated successfully, but these errors were encountered: