1c3926332f
P0-8: re-verified the ~178-key admin i18n gap (docs/KNOWN-ISSUES.md item 2, docs/ADMIN-UX-AUDIT.md) is largely fixed by prior commits, but a live pass over Orders/Transactions/Users/Monitoring/Analytics found 2 remaining leaks: - adminOrders.status.all rendered literally in the Orders list's primary status filter (the bulk-action status select already excluded 'all' and was fine; the primary filter loop did not). - adminUsers.suspend / adminUsers.reactivate rendered literally on every row action button on the Users page. Added the missing keys to all 3 locales. Transactions, Monitoring, and Analytics show no raw dot-key leaks in this pass. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Marketplace Frontend
Angular marketplace frontend for the client demonstration. The app uses standalone components, signals, runtime branding/configuration, and a production build optimized for the current marketplace experience.
Features
- Responsive marketplace storefront
- Category browsing and product detail pages
- Search and shopping cart flows
- Telegram login integration
- Payment handoff through the existing backend contract
- Runtime branding and configuration loading
- PWA manifest and service worker configuration
Development
Install dependencies:
npm install
Start the local development server:
npm start
Build for production:
npm run build
The production build is written to dist/dexarmarket/.
Project Structure
src/
├── app/
│ ├── components/ # Shared storefront components
│ ├── core/ # Runtime, config, guards, providers, interceptors
│ ├── dynamic-renderer/ # Page, section, and widget rendering pipeline
│ ├── facades/ # Runtime, website, builder, and backoffice facades
│ ├── pages/ # Storefront, info, legal, cart, search, and item pages
│ ├── services/ # API, cart, auth, SEO, Telegram, and language services
│ └── widgets/ # Dynamic renderer widgets
├── assets/mock/ # Local mock configuration and catalog data
├── environments/ # Development and production environment settings
└── styles/ # Shared global styles and themes
Useful Checks
npm run build
npm run arch:check
Notes
- Authentication and payment integrations are intentionally left on their existing contracts.
- Renderer and runtime architecture should remain stable during demo preparation.
- Client-facing content should avoid placeholder names, mock labels, and temporary routes.