a39b3429ba75360da1e7dafd061d0821b4925eff
P0-5: some catalog listings (live backend data, proxied third-party marketplace via novo.market) carry HTML-entity-encoded markup in their description field, e.g. '<attention>...</attention>' and '"AppStops"' — rendered verbatim as visible text on search-result cards and the PDP description tab. Added a pure cleanDescription() util (item.utils.ts) that decodes the common HTML entities and strips any resulting tag-like markup, then wired it into ProductCardComponent (covers Home/Catalog/Search/ Wishlist/Compare/PDP-similar) and ProductDescriptionComponent (PDP description tab). Output stays a plain string rendered via text interpolation (never innerHTML), so this only cleans up display — it introduces no HTML-rendering/XSS surface. 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.
Description
Languages
TypeScript
71.4%
HTML
15.3%
SCSS
11.9%
Shell
1.3%
JavaScript
0.1%