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

The WhatsApp screen on a phone asks you to pick from a list it does not show

Aperta
  • Qualcosa non va?
#261 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
78/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
go, react, typescript
Ambito
frontend, mobile

Direzione di ricerca

Start with plugins/whatsapp/frontend/Empty.tsx and the mobileSidebar and mobileContent areas under packages/edit-site/src/components/site-editor-routes/ to understand the small-screen pattern. Check how sdk/frontend/index.ts exposes useMediaQuery and SMALL_VIEWPORT, then run the new frontend/src/test/small-shell.test.tsx and the thread test in test/e2e/tests/responsive.spec.ts. Done means the list appears on the /whatsapp page on small screens, while wide screens retain the empty state.

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

Descrizione

bug help wanted

What happens

On a phone, and on any screen under 1024 pixels wide, the admin folds its sidebar into a drawer behind the menu button. At /whatsapp the conversation list is the section's sidebar, so it goes into the drawer too. The page itself shows only the empty state "No conversation selected. Pick one from the list to read its messages." No list appears on the page. A new user has to guess that the menu button holds it.

What should happen

Under 1024 pixels, /whatsapp shows the conversation list on the page, under the Conversations title, instead of the empty state. Tapping a conversation opens its thread, as it does today. On a wide screen nothing changes. The list stays in the sidebar and the page keeps the empty state. The drawer keeps the WhatsApp screen and its back link to the main menu.

WordPress does the same in the Site Editor. Below its medium breakpoint, the Navigation screen drops the preview and fills the screen with the list of menus. The Patterns screen shows the list of categories first, and shows the patterns only after you pick one. See the mobileSidebar and mobileContent areas in packages/edit-site/src/components/site-editor-routes/.

Where

  • plugins/whatsapp/frontend/Empty.tsx, render ConversationList when the viewport is small
  • sdk/frontend/index.ts, export useMediaQuery and SMALL_VIEWPORT from @gopherium/godmin. That is the query the frame folds its rail at.
  • frontend/src/index.css, the .alphone-conversation rows, so they read well on the light page
  • frontend/src/test/small-shell.test.tsx, a new test. With a small viewport, /whatsapp shows a conversation link on the page without opening the drawer. With a wide viewport, the empty state stays.
  • test/e2e/tests/responsive.spec.ts, the thread test taps the conversation on the page instead of opening the drawer
Lingua principale
Go
Stelle
287
Fork
64
Merge medio
13h 19m
PR unite (30g)
62

Preparare l'ambiente

  • Include un Dockerfile o un file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

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 gopherium/AlphOne

Tutte le issue di gopherium/AlphOne

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.