Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Improve Blocked Words UX and Real-Time Engine Filtering

Aberta
  • Algo errado?
#387 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
48/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Pouca atividade
Stack de tecnologia
android, kotlin
Domínio
mobile-dev

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.
Linguagem predominante
Kotlin
Estrelas
1k
Forks
59
Merge médio
13h 11min
PRs com merge (30d)
47

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de LeanBitLab/LeanType

Todas as issues de LeanBitLab/LeanType

Issues semelhantes

Mais issues de Kotlin

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.