Apostrophe in the custom option is ignored
Open
Nobody has claimed this yet.
bug
- Dominant language
- JavaScript
- Stars
- 608
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
Expected behavior:
```
>limax("wendy's", {custom: ["'"]})
wendy's
```
Actual behavior:
```
>limax("wendy's", {custom: ["'"]})
wendys
```
The `separateApostrophes` option does not help here.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Reproduce the issue with limax("wendy's", {custom: ["'"]}) and trace how the custom and separateApostrophes options are handled. Done means the apostrophe is retained as shown in the expected output and a regression test covers this case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100