mirror of
https://github.com/healthchecks/healthchecks.git
synced 2026-04-24 22:45:56 +03:00
[GH-ISSUE #1131] Feature request: Mixed case slugs #783
Labels
No labels
bug
bug
bug
feature
good-first-issue
new integration
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/healthchecks#783
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @lyonzy on GitHub (Mar 5, 2025).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/1131
Hey there,
I'm trying to monitor backup completion events from a Synology NAS and the best I can get it to send is the mixed-case backup task name e.g.
...url.../LUN-1. Would you be interested in adding maybe an environment variable to disable the requirement for lowercase slugs? Or possibly making the check just a warning rather than a showstopper?In the meantime I've gathered it's a client-side check so I've just changed the database directly, but I'd rather get it changed formally in case you one day rely on them being lowercase.
Thanks,
Matt
@lyonzy commented on GitHub (Mar 5, 2025):
I should add it's a bit of a niche use case, I have 7 LUNs and I want a health check for each, so I've found a way to put the task name in the URL. If anyone just has a single backup task they could just hardcode the ping URL.
@cuu508 commented on GitHub (Mar 10, 2025):
Thanks for the suggestion, but I'd like to stick with lower-case slugs. I've called them slugs everywhere (in code, docs, blog posts), and URL slugs are traditionally lower-case. Allowing mixed case would mean we're allowing in strings that do not look like slugs, and call them "slugs" anyway.