Name length cap: is 40 right, should it apply to tracker names, or should long slugs be shortened instead?
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start by reading the change in #286 and its validate_name implementation, then trace how branch.slug and tracker names feed project IDs, Docker Compose names, paths, refs, and remote repository names. Check the actual naming limits for Supabase and Docker, then compare a shared cap with limits tailored to each use. Done means the issue's questions have a measured, documented decision and the validation behavior matches it.
Written by the indexing model from the issue text.
Description
#286 (for #263) caps names at MAX_NAME_LEN = 40 in validate_name. The number came from reasoning, not measurement:
- Is 40 right? The slug feeds
{{branch.slug}}: Supabaseproject_ids (<prefix>-{{branch.slug}}), Docker Compose project and container names (supabase_realtime_<project_id>), the workspace directory and the lock file. A 63-character DNS label is the tightest plausible limit, and 40 leaves 23 characters for a prefix. Nobody has checked it against Supabase's or Docker's actual rules, and branches named after long issue titles will hit it. - It also caps tracker names.
validate_nameis shared, so tracker and code-tracker names get the same 40-character limit. They're spliced into paths, refs and remote repo names (<owner>.<project>.t.<tracker>), so a cap is reasonable, but maybe not the same one. - Should the cap depend on what the name feeds? An alternative is to allow longer names and shorten the slug (truncate plus a hash) wherever it goes into Docker or Supabase identifiers.
- Dominant language
- Rust
- Stars
- 0
- Forks
- 0
- Avg merge
- 4h 56m
- Merged PRs (30d)
- 51
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Spheroman/newgit
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
`tracker list` leaves out trackers with no `paths`Possibly taken @Spheroman claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Port allocation order within a resource is unspecifiedPossibly taken A pull request linked to this issue is open or already merged. Opendocumentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Spheroman/newgit#59 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
All issues in Spheroman/newgit
Similar issues
-
bug dependencies kind:fix priority: P3 ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
shep-pm/shep#1318 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
swc-project/swc-next#1165 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Alive24/shea-symphony#574 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Maintainers usually reply within 1 day