Autocompletion Meta Issue

Aberta
#445 0 comentários 3 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 2 dias

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
15/100
Tipo de issue
Funcionalidade
Clareza
Precisa de esclarecimento
Status de atividade
Estagnada
Stack de tecnologia
ruby
Domínio
cli, tooling

Direção de pesquisa

Comece revisando os problemas não marcados e as issues referenciadas #351, #328 e #339, juntamente com a issue relacionada do Reline #485. A issue propõe abrir issues de acompanhamento separadas, portanto sua conclusão exigiria identificar e documentar soluções acionáveis para os problemas restantes de autocompletar.

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

Descrição

bug

Background

Since its introduction in version 1.4.0, the autocompletion feature has received mixed feedback. We can see many issues and comments in the repo mentioning its problems. Personally I find the feature useful and pretty like it, but I also experienced some problems with it.

However, many feedback were given through various channels (GH issues, Twitter, Slack channels...etc.). And from my experience, people mentioned different problems, not just one.

So I decided to reach out to the community to ask how they feel about this feature, as well as the specific problems they experienced. And then combine with feedback I collected from other channels, I would make a list of problems, so we can discuss and solve them more effectively.

My Poll Results

I did 2 polls, on one Twitter and another one on ruby.social:

Poll on Twitter Poll on ruby.social

We can see that in both polls:

  • Users generally feel this feature is helpful
  • But more than half of them think it has issues
  • There's a non-small percentage of users decided to disable it completely

Problems Collected From Users

Based on the comments from these polls as well as comments in related GH issues, I think we can list its common issues (ordered by frequency):

What's Next?

I'll open an issue for every problem if they don't already have one, start from the top of the list.

If the problem involves changing other libraries, like reline, I'll propose the changes on Ruby issue tracker as well (like this one for background colour issue). And in those issues/tickets, we can have more detailed discussions.

Linguagem predominante
Ruby
Estrelas
477
Forks
165
Merge médio
1d 19h
PRs com merge (30d)
5

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 ruby/irb

Todas as issues de ruby/irb

Issues semelhantes

Mais issues de Ruby

Receba novas issues na sua caixa de entrada

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