starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 13:53:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

transliterate Umlauts in autogenerated slugs #5747

New Issue
Closed
opened 2025-12-29 19:32:08 +01:00 by adam · 9 comments
adam commented 2025-12-29 19:32:08 +01:00
Owner
Copy Link

Originally created by @lucasteinke on GitHub (Dec 9, 2021).

NetBox version

v3.1.0

Feature type

Change to existing functionality

Proposed functionality

Currently, the autogenerated slugs just omit Umlauts, so when you for example enter Döner GmbH & Co. KG as tenant name, the slug generated will be dner-gmbh-co-kg. It would be nice if Umlauts could be transliterated, so ä➔ae, ö➔oe, ü➔ue.

Maybe you can also transliterate stuff like & to and. Possibly there are other transliterations possible for other special characters in other languages.

Use case

There would be readable slugs without having to change the slug manually.

Database changes

No DB changes.

External dependencies

No new dependencies.

Originally created by @lucasteinke on GitHub (Dec 9, 2021). ### NetBox version v3.1.0 ### Feature type Change to existing functionality ### Proposed functionality Currently, the autogenerated slugs just omit Umlauts, so when you for example enter `Döner GmbH & Co. KG` as tenant name, the slug generated will be `dner-gmbh-co-kg`. It would be nice if Umlauts could be transliterated, so `ä`➔`ae`, `ö`➔`oe`, `ü`➔`ue`. Maybe you can also transliterate stuff like `&` to `and`. Possibly there are other transliterations possible for other special characters in other languages. ### Use case There would be readable slugs without having to change the slug manually. ### Database changes No DB changes. ### External dependencies No new dependencies.
adam added the type: featurestatus: needs ownerpending closure labels 2025-12-29 19:32:08 +01:00
adam closed this issue 2025-12-29 19:32:09 +01:00
adam commented 2025-12-29 19:32:09 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Dec 9, 2021):

Is there a javascript library to handle this automatically?

@DanSheps commented on GitHub (Dec 9, 2021): Is there a javascript library to handle this automatically?
adam commented 2025-12-29 19:32:10 +01:00
Author
Owner
Copy Link

@markkuleinio commented on GitHub (Dec 9, 2021):

I thought slugs were being phased out, please remind me how it is. I mean, if slugs are here still to stay, then as a Finnish name user I would support this.

Hämäläinen -> hmlinen... 😊🇫🇮

@markkuleinio commented on GitHub (Dec 9, 2021): I thought slugs were being phased out, please remind me how it is. I mean, if slugs are here still to stay, then as a Finnish name user I would support this. Hämäläinen -> `hmlinen`... 😊🇫🇮
adam commented 2025-12-29 19:32:10 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 9, 2021):

I thought slugs were being phased out

I'm not sure to be honest. I think it makes sense, however a number of people do utilize the slug field to store import data (e.g. site codes). It would actually simplify things a good deal if we ditched them, but we need to ensure that anyone who needs slugs has a suitable migration path.

@jeremystretch commented on GitHub (Dec 9, 2021): > I thought slugs were being phased out I'm not sure to be honest. I think it makes sense, however a number of people do utilize the slug field to store import data (e.g. site codes). It would actually simplify things a good deal if we ditched them, but we need to ensure that anyone who needs slugs has a suitable migration path.
adam commented 2025-12-29 19:32:10 +01:00
Author
Owner
Copy Link

@mmfreitas commented on GitHub (Dec 9, 2021):

I thought slugs were being phased out

I'm not sure to be honest. I think it makes sense, however a number of people do utilize the slug field to store import data (e.g. site codes). It would actually simplify things a good deal if we ditched them, but we need to ensure that anyone who needs slugs has a suitable migration path.

I thought that the slug was for a functional part of netbox such as url creation and querying. If it is not that important maybe it doesn't make sense being there...?
It also doesn´t seem like the type of field to store the type of information that you mentioned, I believe that would be better suited for a custom field and therefore it would be up to the user to migrate this information as you cannot prepare for every use case scenario.

@mmfreitas commented on GitHub (Dec 9, 2021): > > I thought slugs were being phased out > > I'm not sure to be honest. I think it makes sense, however a number of people do utilize the slug field to store import data (e.g. site codes). It would actually simplify things a good deal if we ditched them, but we need to ensure that anyone who needs slugs has a suitable migration path. I thought that the slug was for a functional part of netbox such as url creation and querying. If it is not that important maybe it doesn't make sense being there...? It also doesn´t seem like the type of field to store the type of information that you mentioned, I believe that would be better suited for a custom field and therefore it would be up to the user to migrate this information as you cannot prepare for every use case scenario.
adam commented 2025-12-29 19:32:10 +01:00
Author
Owner
Copy Link

@markkuleinio commented on GitHub (Dec 9, 2021):

My biggest problem with slugs is that they are mandatory fields so I need to generate them in my apps. Currently I use random strings because it's easier than trying to generate the slug based on the object name and then double-checking that it really is unique within the object model.

@markkuleinio commented on GitHub (Dec 9, 2021): My biggest problem with slugs is that they are mandatory fields so I need to generate them in my apps. Currently I use random strings because it's easier than trying to generate the slug based on the object name and then double-checking that it really is unique within the object model.
adam commented 2025-12-29 19:32:10 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 9, 2021):

I thought that the slug was for a functional part of netbox such as url creation and querying.

We standardized all URL paths to use numeric keys only a while back (v2.11 maybe?).

It also doesn´t seem like the type of field to store the type of information that you mentioned, I believe that would be better suited for a custom field and therefore it would be up to the user to migrate this information as you cannot prepare for every use case scenario.

Agreed; a custom field would probably be the way to go.

@jeremystretch commented on GitHub (Dec 9, 2021): > I thought that the slug was for a functional part of netbox such as url creation and querying. We standardized all URL paths to use numeric keys only a while back (v2.11 maybe?). > It also doesn´t seem like the type of field to store the type of information that you mentioned, I believe that would be better suited for a custom field and therefore it would be up to the user to migrate this information as you cannot prepare for every use case scenario. Agreed; a custom field would probably be the way to go.
adam commented 2025-12-29 19:32:11 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 10, 2021):

I've opened #8036 to propose removing slugs entirely.

@jeremystretch commented on GitHub (Dec 10, 2021): I've opened #8036 to propose removing slugs entirely.
adam commented 2025-12-29 19:32:11 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Feb 9, 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 (Feb 9, 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:32:11 +01:00
Author
Owner
Copy Link

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

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[bot] commented on GitHub (Mar 11, 2022): 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.
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 pending closure status: needs owner 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#5747
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?