Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Improve Blocked Words UX and Real-Time Engine Filtering

Abierto
  • ¿Algo no está bien?
#387 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
android, kotlin
Área
mobile-dev

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.
Lenguaje dominante
Kotlin
Estrellas
1k
Forks
59
Merge medio
13 h 21 min
PR fusionados (30 d)
48

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de LeanBitLab/LeanType

Todos los issues de LeanBitLab/LeanType

Issues similares

Más issues de Kotlin

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.