Auto-capitalization patterns
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
Start by reading the keyboard’s existing auto-capitalization and dictionary or text-expander settings to find where capitalization rules are handled. The issue proposes user-defined patterns, possibly with regex, but does not name files or tests. Done means users can configure patterns such as after “(” and choose whether the next letter is capitalized.
Written by the indexing model from the issue text.
Description
Currently, auto-capitalization only work on certain scenerios, all is determined by the app. I'll be really useful if user can make a pattern for their auto-capitalization settings. For example, some user may want their keyboard to auto-capitalized after "(", "(Abc). Some user may not.
The way it works is just like dictionary, or text expander. User can enter a pattern (maybe it can support regex) in which the next letter will be capitalized.
For example (the • character is not included):
• “• ( “Abc)
•.” • (.” Abc)
•{• ({Abc)
- Dominant language
- Kotlin
- Stars
- 1k
- Forks
- 59
- Avg merge
- 13h 11m
- Merged PRs (30d)
- 47
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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 LeanBitLab/LeanType
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
LeanBitLab/LeanType#713 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
LeanBitLab/LeanType#423 · 1 comment ·
Maintainers usually reply within 1 day
-
Crush ReportOpen
Difficulty 3/5 1-2 days Newbie friendliness 20/100
LeanBitLab/LeanType#715 ·
Maintainers usually reply within 1 day
-
Text Expander/cursor-handling bugPossibly taken @LeanBitLab claimed this 2 days ago. Openbug
Difficulty 3/5 1-2 days Newbie friendliness 62/100
LeanBitLab/LeanType#703 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 45/100
LeanBitLab/LeanType#699 ·
Maintainers usually reply within 1 day
All issues in LeanBitLab/LeanType
Similar issues
-
afk-ok area:data-quality importer size:S
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
enorm-labs/event-junkie#3767 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
leboncoin/spark-android#2342 ·
Maintainers usually reply within 1 day
-
The Voraton URL has been changedPossibly taken A pull request linked to this issue is open or already merged. OpenBug Domain changed
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
keiyoushi/extensions-source#20257 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
user-grinch/RivoPhoneApp#302 ·
Maintainers usually reply within 1 day