fd7ffc8668
Exhaustive inventory of every HTTP call, gateway (interface + mock + real impl), facade, and model/DTO the frontend defines or expects, grouped by domain. Primary input for the remaining Backend Finalization Sprint docs. Key findings: - Only AdminCategoriesGateway and AdminDashboardMetricsGateway are DI-token-bound; every other admin domain (orders, products, users, transactions, monitoring, moderation) injects its *LocalGateway class directly - a real backend swap needs a token added first, not just a rebind. - Only one real admin API impl exists (AdminCategoriesApiGateway); everything else admin is in-memory/localStorage mock. - Content-management/project-editor have no save/publish HTTP call at all - builder writes are in-memory + localStorage draft only. - No literal /admin|/builder|/backoffice CRUD paths exist in source; concrete admin paths are proposals, not verified literals.
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.