Autocompletion Meta Issue

Abierto
#445 0 comentarios 3 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
15/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
ruby
Área
cli, tooling

Línea de trabajo

Comienza revisando los problemas no marcados y los issues referenciados #351, #328 y #339, junto con el issue relacionado de Reline #485. El issue propone abrir issues de seguimiento separados, por lo que completarlo requeriría identificar y documentar soluciones prácticas para los problemas restantes de autocompletado.

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

Descripción

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.

Lenguaje dominante
Ruby
Estrellas
477
Forks
165
Merge medio
1 d 19 h
PR fusionados (30 d)
5

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

Todos los issues de ruby/irb

Issues similares

Más issues de Ruby

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.