nixgram / zcommerce

An Open-Source E2E-Ecommerce API Provider

This is an API solution & also template for support minimal e-commerce application using .NET5 following the principles of Clean Architecture inspire from Jason Taylor. Use this template button or by installing and running the associated NuGet package (see Getting Started for full details). It's easy to jump start from beginning you can try it the barebone project v0.0.1-beta

Recommend to learn Clean Architecture with ASP.NET Core 3.0 • Jason Taylor • GOTO 2019

Technologies

• NET5
• Entity Framework Core 5
• MediatR
• AutoMapper
• FluentValidation
• XUnit, FluentAssertions, Moq & Respawn
• SQLite

Getting Started

1. Install the latest .NET 5 SDK
2. Install Redis using docker & run docker run -d --rm -p 6379:6379 redis
3. Go to ZCommerce.API & Run dotnet run to run this project template

Database Migrations

To use dotnet-ef for your migrations please add the following flags to your command (values assume you are executing from repository root)

• --project ./src/Infrastructure (optional if in this folder)
• --startup-project ./src/Api
• --output-dir Data/Migrations

For example, to add a new migration from the root folder:

dotnet ef migrations add "SampleMigration" --project ./src/Infrastructure --startup-project ./src/Api --output-dir Data/Migrations

Update Database,

dotnet ef database update --project ./src/Infrastructure --startup-project ./src/Api

Overview

ZCommerce.Domain

This will contain all entities, enums, exceptions, interfaces, types and logic specific to the domain layer.

ZCommerce.Application

This layer contains all application logic. It is dependent on the domain layer, but has no dependencies on any other layer or project. This layer defines interfaces that are implemented by outside layers. For example, if the application need to access a notification service, a new interface would be added to application and an implementation would be created within infrastructure.

ZCommerce.Infrastructure

This layer contains classes for accessing external resources such as file systems, web services, smtp, and so on. These classes should be based on interfaces defined within the application layer.

ZCommerce.API

This layer contain all API end points and contract with ZCommerce.Application via MediatR.

Support

If you are having problems, please let us know by raising a new issue.

License

This project is licensed with the MIT license.

Connect with me

zcommerce's Issues

Custom global exception middleware

• FluentExceptionValidation Using ErrorDescriptor class with ErrorHandlingMiddleware

Add If you have more ideas

Publishing docker image to docker hub

Feature :
[ will be added soon ]

More on Common

• Refresh Token
• Password Changing
• Password Forget [ only for customer via email ]
• Report
• Feature Request

Publish postman API documentation

• Invoice
• Login
• Register
• Product
• Product Category

User Creation

• Role Claim Type
  • Customer
  • Admin
• Registration
  • Customer
• Login via user claim type

Product [ For Admin ]

Class list is bellow -

• Product - Minimal Information with Single Entry
• Vendor Entry
• Product Category
• Update Product
• Disable Product ( Haven't Delete Option )
• Image can update separately

Completing basic guide of this project in readme file

• Introduction of this project
• Technology Stack
• Get Started
• Contribution Guide

External Connections

• Connect with Redis
• Connect with Azure Redis
• Docker
• Docker Compose
• Docker hub CI/CD
• Azure WebAPP

Admin Dashboard

• Orders
• Shipment Status
• Pending Order
• Sending Email to customer
• Active Customer in online
• Cancel Order Tracking
• Customer Support ( Messaging )

Customer Dashboard

• Profile Update
• Orders
• Order Cancel
• Order Tracking
• Bonus
• Support ( Messaging )

This line is duplicate in the same block.

ZCommerce/src/Api/Startup.cs

Line 53 in 01587f1

app.UseMiddleware<ErrorHandlingMiddleware>();

Multiple DB Context

• SQL Server
• Mongo DB
• My Sql
• SQLite

Making template for Jumpstart

💡 Need to complete before making template for Jumpstart

• Basic User claim options
• Basic Invoice Management API endpoint for understanding this project hypothesis
• Making for scaling with pure CQRS concept
• Identity Server
• Implementing Basic Redis Distribution Cache extension [ using Docker ]
• Release v-0.0.1-beta

Role Assignee Controller [ Only Admin Can Assign Role ]

• If role not found then create & assign.
• A user have multiple role
• Admin can not assign admin role to a user