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.

Sign up for GitHub

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

Jump to bottom

Replace "obj" context var with "object" for custom links #8684

Closed
jeremystretch opened this issue Feb 18, 2022 · 0 comments
Closed

Replace "obj" context var with "object" for custom links #8684

jeremystretch opened this issue Feb 18, 2022 · 0 comments
Assignees
@jeremystretch
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application

Comments

@jeremystretch
Copy link
Member

NetBox version

v3.1.8

Feature type

Change to existing functionality

Proposed functionality

Direct users to use object in custom link text and URL templates instead of obj. Both variables will be supported until NetBox v3.5, which will remove support for the old obj variable.

Use case

object is a more natural name for the variable. obj was originally chosen (perhaps without much consideration) because it matched the underlying code. object is a reserved word in Python, but there is no technical reason not to use it in Jinja2 templates.

Database changes

No response

External dependencies

No response
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application labels Feb 18, 2022
@jeremystretch jeremystretch self-assigned this Feb 18, 2022
jeremystretch added a commit that referenced this issue Feb 18, 2022
@jeremystretch
Closes #8684: Change custom link template context variable 'obj' to '…
a5c8bbf 
…object' (backward-compatible)
This was referenced Apr 5, 2022
Closed
Merged
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 20, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jeremystretch jeremystretch

Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jeremystretch