How qiushuangju/qshop works
Project Type and Purpose
• This is a full-stack, front-end/back-end-separated e-commerce system (“QShop商城”) comprising:
• Backend: .NET 6 solution (QShop.sln) with layered architecture (API, Application, Repository, Shared).
• Mobile Frontend: Uni-App cross-platform app (2_UniApp).
• Admin Frontend: Vue.js + Element-UI + Ant-Design-Vue administration portal (3_PcAdmin).
• Database: MySQL (initialization in 8_数据库脚本/MySql初始化.sql).
• External services: shipping (KuaiDi100, KuaiDiNiao), SMS, WeChat Pay, third-party auth.
File Structure
• Top-level directories:
1_Api:
• Qs.WebApi – ASP.NET Core WebAPI project exposing REST controllers.
• Qs.App – Application/business logic layer (services, jobs, strategies).
• Qs.Repository – Data access (Entity models, Repository & UnitOfWork).
• Qs.Comm – Shared utilities, caching, middleware, config, Snowflake ID generator.
2_UniApp: Mobile client source (pages, components, API wrappers, store).
3_PcAdmin: Admin portal (Vue.js project, API calls, components, views).
8_数据库脚本: DB DDL.
• Architectural choices: layered (Presentation → API → Application → Repository → Database), Strategy pattern for auth, Factory for express providers, Repository & UnitOfWork patterns, Hosted background jobs via Quartz.
README
• Confirms: front/back separation, .NET6, WebAPI, Swagger, NUnit tests, Uni-App, Vue/Element-UI, Ant-Design-Vue, RBAC, open-source.