Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Improve Blocked Words UX and Real-Time Engine Filtering

Offen
  • Stimmt etwas nicht?
#387 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
48/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Ruhig
Tech-Stack
android, kotlin
Bereich
mobile-dev

Rechercherichtung

Start by tracing the suggestion-chip long-press and delete-state handling, including the postDelayed timeout and DICTIONARY_USER_TYPED restriction. Then read the engine's raw-input filtering and dictionary reload paths, along with how blacklist .txt files are loaded. Done means only one word's delete control is active until dismissed, typed words can be blacklisted, and blacklisted words are suppressed from both raw input and suggestions.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

enhancement
Current Limitations
  1. UX Constraints: The delete (bin) icon on suggestion chips disappears automatically after a 3-second timeout (postDelayed), and it is completely disabled for raw user-typed words (DICTIONARY_USER_TYPED).
  2. Real-time Filtering: Blacklisted words can still appear during active typing because the filter only applies to dictionary suggestions, not the raw input stream.
Proposed Solutions
1. UI & State Management Improvements
  • Remove the 3-second timeout (postDelayed). Ensure that only one word can be in delete mode at a time—long-pressing a new word must instantly clear the bin icon from the previous word. Let the delete state persist until the user taps the bin or interacts elsewhere.
  • Track a single active delete view state so long-pressing a new word automatically resets the previous one.
  • Remove the restriction on DICTIONARY_USER_TYPED so users can delete and blacklist any word they type.
2. Engine-Level Filtering with Zero Performance Impact (Caching)
  • To prevent heavy file I/O or lag on every keystroke, load the blacklist .txt files into an in-memory HashSet upon initialization or dictionary reload.
  • Perform real-time checks against this in-memory Set (microseconds lookup time). This ensures blacklisted words are completely suppressed from both raw typing and suggestions without adding any performance overhead or lag to the core engine.
Vorherrschende Sprache
Kotlin
Sterne
1k
Forks
59
Ø Merge
13 Std. 11 Min.
Gemergte PRs (30 T.)
47

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus LeanBitLab/LeanType

Alle Issues in LeanBitLab/LeanType

Ähnliche Issues

Weitere Issues zu Kotlin

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.