Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Command palette could use some love

Abierto
  • ¿Algo no está bien?
#15,281 2 comentarios 1 reacción 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
laravel, php
Área
frontend

Línea de trabajo

Start by reproducing the reported command-palette issues with multiple collections and entries, especially keyboard navigation, slow-loading results, filtering, and recent items. The issue names no files or tests; use the reproductions to locate the relevant entry points and define which reported behaviors are in scope, then verify those behaviors are corrected.

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

Descripción

command palette ui
Bug description

The command palette is great in theory for quickly navigating items within the CP. But in practice I find it unreliable and it often takes more time than it would've by just clicking around in the CP.

If it's ok, I'll list some stuff I've noticed:

  • Sometimes you can't keyboard navigate the results by going down, you have to go up and then it jumps to the last result.
  • Results often load in slow and then active items lose focus.
  • Search seems to broad. When I type in something like "Issue 1", I get all collection items called Issue (2, 3, 4, 5).
  • I have a collection with similar entry titles. So when I search for Issue $collectionTitle I would've hoped the results filter. Instead doing exactly this gives me the search results from the $collectionTitle I haven't included. Which seems odd.
  • Recent items often don't seem to populate with recent items
  • You can't cmd+enter to open items in a new tab
  • Appropriate results aren't always the first ones listed
How to reproduce

Play with the thing, especially when you've got multiple collections and entries.

Environment
Environment
Laravel Version: 13.29.0
PHP Version: 8.5.8
Composer Version: 2.10.1
Environment: local
Debug Mode: ENABLED
Maintenance Mode: OFF
Timezone: UTC
Locale: en

Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: CACHED

Drivers
Broadcasting: log
Cache: file
Database: sqlite
Logs: stack / single
Mail: smtp
Queue: sync
Session: file

Storage
public/storage: NOT LINKED

Statamic
Addons: 5
License Key: Set
Sites: 1
Stache Watcher: Enabled (auto)
Static Caching: Disabled
Version: 6.29.0 PRO

Statamic Addons
rias/statamic-color-swatches: 3.1.1
statamic-rad-pack/shopify: 7.8.3
studio1902/statamic-peak-commands: 11.1.0
studio1902/statamic-peak-seo: 11.9.2
studio1902/statamic-peak-tools: 9.2.0
Installation

Fresh statamic/statamic site via CLI

Additional details

No response

Lenguaje dominante
PHP
Estrellas
4.9k
Forks
647
Merge medio
1 d 7 h
PR fusionados (30 d)
103

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 statamic/cms

Todos los issues de statamic/cms

Issues similares

Más issues de PHP

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.