sdarbinyan 097927f124
Some checks failed
Architecture Governance / architecture (push) Has been cancelled
feat(admin): implement order and customer operations experience
Orders dashboard (real orders-today/pending/paid/cancelled/refunded/customers/returning-customers/average-order/recent-activity/system-alerts, computed from the full order book not just the current page); orders list gains density, saved column visibility, bulk status change/archive/delete/export/print alongside existing search+status filter+pagination, sticky table header; order detail gets a visual status workflow stepper in business language (Pending/Packing/Shipping/Completed, with Cancelled/Refunded as terminal states) and a reusable OrderTimelineComponent replacing the flat text log; added a derived Customers feature (list + profile detail: statistics/lifetime value/addresses/orders/activity/notes) built entirely by grouping existing AdminOrder records by email - no new backend, no invented gateway, since no customer entity existed. Added archive/restore/delete to the orders gateway (soft-delete pattern mirroring categories) and filled in the adminOrders/adminCustomers i18n namespaces, which previously didn't exist at all (every adminOrders.* label was rendering as a raw key).
2026-07-18 21:47:54 +04:00
2026-01-18 18:57:06 +04:00
2026-06-01 00:47:26 +04:00
2026-01-18 18:57:06 +04:00
2026-07-16 00:22:01 +04:00
2026-03-24 02:25:50 +04:00
2026-07-09 01:40:22 +04:00
2026-07-05 00:57:20 +04:00
2026-07-16 00:22:01 +04:00
2026-05-28 12:56:41 +00:00
2026-01-18 19:44:46 +04:00
2026-06-21 23:42:39 +04:00

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
No description provided
Readme 16 MiB
Languages
TypeScript 71.4%
HTML 15.3%
SCSS 11.9%
Shell 1.3%
JavaScript 0.1%