scribe-org / scribe-org/Scribe-Android
Remove profanity from autosuggestions and autocompletions
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 99
- Forks
- 121
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 16
Description
Terms
- I have searched open and closed feature requests
- I agree to follow Scribe-Android's Code of Conduct
Description
[!NOTE]
This issue is blocked by the following issues:
We need to remove profanity from the autosuggestions and autocompletions for the keyboard application. This can be done once we export the profanity table as a part of Scribe-Data and then serve this data from Scribe-Server. The work to do this is done in the above listed issues in the note.
The way that we'll do this is remove any strings that contain a profane word from autosuggestions or autocompletions and move to the next word for the displayed field.
Contribution
Happy to support on this and review a PR! 😊
Contributor 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.
Research direction
Start by reviewing PR #660 and the linked Scribe-Data #710 and Scribe-Server #75 work, since this issue is blocked on those changes. Then locate the Android autosuggestion and autocompletion entry points and trace how the served profanity data will be consumed. Done means strings containing profane words are skipped and the next word is displayed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100