Nikolay Tatarinov
16bf1a1043
- Replaced the previous webapp with a new Mini App built using Next.js, improving performance and maintainability. - Updated the `.gitignore` to exclude Next.js build artifacts and node modules. - Revised documentation in `AGENTS.md`, `README.md`, and `architecture.md` to reflect the new Mini App structure and technology stack. - Enhanced Dockerfile to support the new build process for the Next.js application. - Updated CI workflow to build and test the Next.js application. - Added new configuration options for the Mini App, including `MINI_APP_SHORT_NAME` for improved deep linking. - Refactored frontend testing setup to accommodate the new structure and testing framework. - Removed legacy webapp files and dependencies to streamline the project.
54 lines
2.8 KiB
Plaintext
54 lines
2.8 KiB
Plaintext
---
|
|
description: Rules for working with the Telegram Mini App frontend (webapp-next/)
|
|
globs:
|
|
- webapp-next/**
|
|
---
|
|
|
|
# Frontend — Telegram Mini App (Next.js)
|
|
|
|
The Mini App lives in `webapp-next/`. It is built as a static export and served by FastAPI at `/app`.
|
|
|
|
## Stack
|
|
|
|
- **Next.js** (App Router, `output: 'export'`, `basePath: '/app'`)
|
|
- **TypeScript**
|
|
- **Tailwind CSS** — theme extended with custom tokens (surface, muted, accent, duty, today, etc.)
|
|
- **shadcn/ui** — Button, Card, Sheet, Popover, Tooltip, Skeleton, Badge
|
|
- **Zustand** — app store (month, lang, duties, calendar events, loading, view state)
|
|
- **@telegram-apps/sdk-react** — SDKProvider, useThemeParams, useLaunchParams, useMiniApp, useBackButton
|
|
|
|
## Structure
|
|
|
|
| Area | Location |
|
|
|------|----------|
|
|
| App entry, layout | `src/app/layout.tsx`, `src/app/page.tsx` |
|
|
| Providers | `src/components/providers/TelegramProvider.tsx` |
|
|
| Calendar | `src/components/calendar/` — CalendarHeader, CalendarGrid, CalendarDay, DayIndicators |
|
|
| Duty list | `src/components/duty/` — DutyList, DutyTimelineCard, DutyItem |
|
|
| Day detail | `src/components/day-detail/` — DayDetail (Sheet/Popover), DayDetailContent |
|
|
| Current duty view | `src/components/current-duty/CurrentDutyView.tsx` |
|
|
| Contact links | `src/components/contact/ContactLinks.tsx` |
|
|
| State views | `src/components/states/` — LoadingState, ErrorState, AccessDenied |
|
|
| Hooks | `src/hooks/` — use-telegram-theme, use-telegram-auth, use-month-data, use-swipe, use-media-query, use-sticky-scroll, use-auto-refresh |
|
|
| Lib | `src/lib/` — api, calendar-data, date-utils, phone-format, constants, utils |
|
|
| i18n | `src/i18n/` — messages.ts, use-translation.ts |
|
|
| Store | `src/store/app-store.ts` |
|
|
| Types | `src/types/index.ts` |
|
|
|
|
## Conventions
|
|
|
|
- **Client components:** Use `'use client'` where hooks or browser APIs are used (layout loads config script; page and most UI are client).
|
|
- **Theme:** CSS variables in `globals.css`; `useTelegramTheme` maps Telegram theme params to `--tg-theme-*` and sets `data-theme` on `<html>`.
|
|
- **Auth:** `useTelegramAuth` provides initData for API; access gated for non-Telegram except localhost.
|
|
- **i18n:** `useTranslation()` from store lang; `window.__DT_LANG` set by `/app/config.js` (backend).
|
|
- **API:** `fetchDuties`, `fetchCalendarEvents` in `src/lib/api.ts`; pass initData, lang, AbortSignal; handle ACCESS_DENIED.
|
|
|
|
## Testing
|
|
|
|
- **Runner:** Vitest in `webapp-next/`; environment: jsdom; React Testing Library.
|
|
- **Config:** `webapp-next/vitest.config.ts`; setup in `src/test/setup.ts`.
|
|
- **Run:** `cd webapp-next && npm test` (or `npm run test`). Build: `npm run build`.
|
|
- **Coverage:** Unit tests for lib (api, date-utils, calendar-data, i18n, etc.) and component tests for calendar, duty list, day detail, current duty, states.
|
|
|
|
Consider these rules when changing the Mini App or adding frontend features.
|