capital_D_dangit?
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- typescript
- Domain
- content
Research direction
The issue jokingly proposes a capital_D_dangit(text: string) helper that rewrites "EmDash" to "Emdash", with a snippet but no target file, call site or acceptance test named. Read the single comment thread first and confirm with maintainers that this novelty function is actually wanted, since it may simply be closed. If accepted, find where user-facing text is normalized in this TypeScript/Astro codebase, place the export in that shared utility, and cover it with a unit test asserting the replacement.
Written by the indexing model from the issue text.
Description
Description
Since EmDash is "the spiritual successor to WordPress", it makes sense that you chose a product name with a capital letter in the middle of it, just like our beloved WP.
You will forever battle your users who just can't find the shift key.
WordPress solves this problem with code, and so can you:
https://developer.wordpress.org/reference/functions/capital_p_dangit/
/**
* Forever eliminate "EmDash" from the planet.
*
* Inspired by WordPress's capital_P_dangit().
*/
export function capital_D_dangit(text: string): string {
return text.replace(/\bEmDash\b/g, 'Emdash');
}
Steps to reproduce
- Go on the internet
- Read about people talking about "Emdash"
Environment
- Emdash
Screenshots
.
Logs / error output
- Dominant language
- TypeScript
- Stars
- 13.4k
- Forks
- 1.3k
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 378
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 emdash-cms/emdash
-
bot:bug bot:needs-attention bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
emdash-cms/emdash#3992 · 2 comments ·
Maintainers usually reply within 2 days
-
bot:bug bot:needs-attention
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
emdash-cms/emdash#3972 · 2 comments ·
Maintainers usually reply within 2 days
-
bot:needs-attention bot:task
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
emdash-cms/emdash#3821 · 1 comment ·
Maintainers usually reply within 2 days
-
area/auth area/cloudflare bot:awaiting-approval bot:bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
emdash-cms/emdash#3702 · 1 comment ·
Maintainers usually reply within 2 days
-
area/plugins bot:awaiting-reporter bot:bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
emdash-cms/emdash#3616 · 4 comments · 1 reaction ·
Maintainers usually reply within 2 days
All issues in emdash-cms/emdash
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 2 days
-
reproduced
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
anomalyco/opencode#62052 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
strapi/design-system#2084 ·
Maintainers usually reply within 3 days
-
check:passed streams:remove
Difficulty 1/5 Under an hour Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
OAuth documentation for GET /api/v2/users/me/ appears inconsistent with required global read scopeOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day