aa308d8258
Bug: AdminCategoriesFacade.reorder(id, targetOrder) took the target
row's numeric order and wrote it straight onto the dragged category
(order: targetOrder). That leaves two siblings tied on the same order
value instead of actually repositioning the dragged item - and since
the local gateway's list sort (Array.prototype.sort, stable) breaks
ties by original array position, drops in certain directions have no
visible effect at all. All seeded categories additionally start at
order: 0 (AdminCategoriesLocalGateway.toAdminCategory), so on fresh
data literally every drag silently no-ops.
Fix: reorder(id, targetId) now takes the target category's id (not
its order value, which can be ambiguous/duplicated), computes the
full sibling sequence with the dragged item spliced into the target's
position, and persists sequential 0..n-1 order values for every
sibling whose order actually changed. Restricted to same-parent
siblings (dragged.parentId !== target.parentId is a no-op, matching
the tree UI's existing scope - no cross-parent move support).
Updated the drag payload end to end: AdminCategoriesListComponent's
`reorder` output now emits { id, targetId } instead of
{ id, targetOrder }; the list page binding follows.
Verified live via window.ng.getComponent() on
/ru/backoffice/categories (devBypassAdmin=true; real backend
unreachable in this environment, so verified against
facade.categories.set([...]) synthetic siblings, consistent with the
gateway calls the facade actually issues):
- Before fix: 3 siblings order 0/1/2, drag 'c' onto 'a' ->
gateway.updateCategory received only { id: 'c', order: 0 }, tying
'a' and 'c' at order 0 (with 0-order seed data, no siblings ever
become distinguishable at all).
- After fix: same drag -> gateway.updateCategory called for 'c', 'a',
'b' with the correct distinct sequence (c:0, a:1, b:2).
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.