a2n-seattle / a2n-seattle/rms-app

Remove Reservation/Return from header nav (dashboard-only access)

Aberta Para iniciantes
#359 2 comentários 0 reações 0 responsáveis Ver no GitHub
idea priority-low
Linguagem predominante
TypeScript
Estrelas
1
Forks
1
Merge médio
27min
PRs com merge (30d)
4

Descrição

# Why?

**As a** user navigating the app
**I want** a simpler header nav
**So that** I'm not offered redundant top-level Reservation/Return entry points when that functionality is already reachable through the Dashboard.

# What?

Remove the "Reservation"/"Return" links from the nav shell (`(protected)/layout.tsx`) — these flows should only be reachable through the Dashboard (alerts, per-item actions, the cart/checkout flow from #359, etc.), not as standalone header nav items.

Confirm no Playwright spec depends on navigating via these header links directly (`golden-path.spec.ts`/`reservations.spec.ts` likely navigate via `page.goto()` directly to routes rather than clicking nav links — verify before removing).

# Testing

Update/remove any Jest/RTL snapshot or nav-link assertions referencing the removed links.

Guia de contribuição

Nenhum guia de contribuição indexado para este repositório

Direção de pesquisa

The change is in the protected layout file at `(protected)/layout.tsx`. Remove the 'Reservation' and 'Return' links from the navigation shell. Check Playwright specs `golden-path.spec.ts` and `reservations.spec.ts` for any direct navigation dependencies. Update or remove Jest/RTL snapshot tests that assert on these nav links. Verify the app still functions via dashboard entry points.

Escrita pelo modelo de indexação a partir do texto da issue.

Avaliação

Stack de tecnologia
nextjs, react
Domínio
frontend
Tipo de issue
Refatoração
Dificuldade
2/5
Tempo estimado
1-3 horas
Status de atividade
Pouca atividade
Clareza
Claramente especificada
Facilidade para iniciantes
70/100

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.