Add support for custom alphabet
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- tooling
Research direction
The issue body names no files, tests, or entry points. Start by locating the encoder entry point and any existing variant tests, then clarify how a custom alphabet should be supplied and validated. Done means the agreed custom-alphabet behavior is implemented and covered by tests.
Written by the indexing model from the issue text.
Description
This issue has no description.
- Dominant language
- JavaScript
- Stars
- 24
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
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.
More from LinusU/base32-encode
-
Difficulty 1/5 Under an hour Newbie friendliness 35/100
LinusU/base32-encode#12 ·
All issues in LinusU/base32-encode
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
[Block] Latest Posts [Type] Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sugarlabs/musicblocks#8847 ·