Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

feat: configurable state inspector page size and stable ordering when showing more object properties

Aperta
#1,143 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
72/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
devtools, frontend

Direzione di ricerca

Start in packages/applet/src/components/state/StateFieldViewer.vue, especially STATE_FIELDS_LIMIT_SIZE and the plain-object property display path. Reproduce the issue with an object of more than 60 properties whose insertion order differs from alphabetical order. Done means the initial count and “Show more” increment are configurable with 30 as the default, and increasing the limit preserves the existing alphabetical row order.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Problem

In the Vue.js Devtools 7.7.7 Chrome extension, expanding an object in the right-hand state pane initially shows 30 properties. Each "Show more" click reveals another 30, but the newly visible properties are mixed alphabetically into the existing rows instead of appearing at the end. This makes it difficult to keep my place while inspecting large objects.

Requested change

Please make the initial property count and "Show more" increment configurable, with options such as 30, 100, and 200. Keeping 30 as the default would preserve current performance behavior.

Please also consider sorting the complete list of object keys before applying the display limit, so increasing the limit appends the next alphabetically ordered batch without shifting previously displayed rows (when the object itself has not changed).

Source reference

In v7.7.7, packages/applet/src/components/state/StateFieldViewer.vue defines STATE_FIELDS_LIMIT_SIZE = 30. For plain objects, it slices Object.keys(value) to the current limit and then sorts the resulting children.

https://github.com/vuejs/devtools/blob/v7.7.7/packages/applet/src/components/state/StateFieldViewer.vue

Example

Inspect a plain object containing more than 60 properties whose insertion order differs from alphabetical order, then expand it and click "Show more". New properties may be inserted above or between previously visible rows.

Alternatives

Repeatedly clicking "Show more" is cumbersome and changes row positions. A configurable larger batch would reduce the number of clicks; sorting before slicing would independently address the changing row positions.

Environment

Vue.js Devtools 7.7.7, Chrome extension.

I searched existing issues and pull requests for "show more", STATE_FIELDS_LIMIT_SIZE, sorting, pagination, and the 30-item limit and did not find a matching request. PR #973 concerns expanding/collapsing nested Pinia structures rather than this pagination behavior.

Lingua principale
TypeScript
Stelle
2.9k
Fork
289
Merge medio
2g 48m
PR unite (30g)
19

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di vuejs/devtools

Tutte le issue di vuejs/devtools

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.