a8a5de5392
Some checks failed
Architecture Governance / architecture (push) Has been cancelled
- EDITOR.md: updated sections table (branding OG/gallery + image-field, header layout/sticky, widgets JSON error feedback), the inline-validation paragraph (now lists every wired fieldKey, not just the original 3 sections), the primitives table (app-image-field, app-code-editor), and a new dated section detailing all 9 fixed bugs plus the 3 real gaps found but deferred (theme mode dead at runtime, dynamic-renderer unwired, header profile menu missing). - KNOWN-ISSUES.md: added the 3 deferred gaps as new Open items, added a Fixed entry summarizing the 9 bugs (points to EDITOR.md for full detail rather than duplicating it). 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.