c069cafe45
Some checks failed
Architecture Governance / architecture (push) Has been cancelled
MediaLibraryFacade is a root-provided singleton shared by every app-media-picker instance on a page (branding alone renders 4; static-pages with N pages renders 2N). ngOnInit called facade.load() unconditionally on mount regardless of whether the dialog was ever opened, and search/folder/ page filters set in one dialog leaked into whichever picker instance was opened next, since they all read/write the same signals. Replaced ngOnInit with an effect() that resets search/folder/page and loads only when this instance's own input becomes true. Verified live: searched in one field's picker, closed it, opened a different field's picker on the same page - search is now reset to empty (previously it would've carried over 'leftover-search-term'). 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.