Add option to preserve username case in zod-transform-socials (GitHub/Twitter/AO3)
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- tooling
Research direction
Start by locating the zod-transform-socials implementation and tracing where the full URL is lower-cased before service matching. Compare the handling needed for GitHub, Twitter/X, AO3, and NPM, then clarify whether the change should use preserveCase, canonicalCase, or both. Done means host detection remains case-insensitive while supported usernames and paths retain the intended case, with observable output and breaking-change behavior documented.
Written by the indexing model from the issue text.
Description
zod-transform-socials lower-cases the whole URL before matching, which means usernames are also lower-cased for services that preserve case. For example, github.com/FujoWebDev/AO3.js is reported as fujowebdev/ao3.js.
Lower-casing is needed for host detection (so BSKY.APP matches bsky.app), but it should not apply to the username (or at least, it should be an option not to apply it).
Among services affected:
- GitHub— org and repo names preserve case.
- Twitter/X — handle display preserves case.
- AO3 — usernames and pseuds preserve case.
- NPM is affected in that older package names could be uppercase/lowercase, but now they're all lowercase. With that said, the install is case sensitive.
This changes observable output, so it is a breaking change. We could mitigate it by adding a preserveCase setting and/or a canonicalCase option for known addresses that one may want to keep consistent. We could also consider exporting convenience methods like "isSameProfile".
- Dominant language
- TypeScript
- Stars
- 27
- Forks
- 7
- Avg merge
- 6m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: 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 FujoWebDev/fujocoded-plugins
-
astro-authproto
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Add generated labels to social link transformsPossibly taken @qianmao1989 claimed this 143 days ago. Opengood first issue zod-transform-socials
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
astro-atproto-loader
Difficulty 3/5 1-2 days Newbie friendliness 65/100
-
astro-authproto
Difficulty 3/5 1-2 days Newbie friendliness 45/100
All issues in FujoWebDev/fujocoded-plugins
Similar issues
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
github/docs#46222 · 1 comment ·
Maintainers usually reply within 1 day
-
agent-ready area: config area: skills type: chore upstream: brain-kit
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
enhancement priority:low ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
bug escritorio mapa
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
marcosferr/reporte-ciudadano#4 · 1 comment ·
-
area: material/sort gemini-triaged needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
angular/components#33933 ·
Maintainers usually reply within 1 day