Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

proposal: Add frame, value decorators

Ouverte
#218 2 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

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

Piste de recherche

The issue does not name files, tests, or entry points. Begin by clarifying the proposed extension API for values, stack frames, and backtraces, then identify the relevant display components; the issue currently does not define concrete completion criteria.

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

Description

enhancement

When I worked on GDB I came to feel that GDB was made so that GDB developers could debug GDB. This was how it was for a long time. But when we added with the Python API to GDB, along with Pretty Printing, frame decorators and filters, we handed back data representation to the user. Don't like how we print this object? Well, here's an API, and the ability to write your own, and hooks back into the display component to write your own representation. What parts of an object or value are important to the developer? It's going to depend on what that developer is trying to solve. So the default GDB information displays were, I think, more or less dependent on the feature implementor: usually what a GDB developer wanted to see when debugging their project (GDB).

So I know this is a super wishy washy proposal right now. But every value printed, every stack frame annotated, every backtrace printed, and so on, should first be offered to any extensions that want to work on them. That way a user can display any value they way they want to display it. If they don't care, well, they'll get the default version. Hopefully I've painted a rough picture of what I would love to see. Any more details, please ask! And if I can find some time, I hope to start putting some patches together.

Langage dominant
Ruby
Étoiles
1.3k
Forks
146
Aucune PR mergée en 30 j

Guide de contribution

Ouvrir le guide de contribution

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/debug

Toutes les issues de ruby/debug

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.