Autocompletion Meta Issue

Ouverte
#445 0 commentaires 3 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 2 jours

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
15/100
Type d'issue
Fonctionnalité
Clarté
À clarifier
Activité
À l'abandon
Stack technique
ruby
Domaine
cli, tooling

Piste de recherche

Commencez par examiner les problèmes non cochés et les issues référencées #351, #328 et #339, ainsi que l’issue associée de Reline #485. L’issue propose d’ouvrir des issues de suivi distinctes ; sa réalisation nécessiterait donc d’identifier et de documenter des solutions concrètes pour les problèmes d’autocomplétion restants.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
Ruby
Étoiles
477
Forks
165
Merge moyen
1 j 19 h
PR mergées (30 j)
5

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de ruby/irb

Toutes les issues de ruby/irb

Issues similaires

Plus d'issues Ruby

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.