v0.1.6

Huge rework of core elements! 🍰

Better structure

All main endpoints now in /core directory.

More focus on tests: unit and e2e

It will be good to cover codebase by all possible tests. Main focus now on services (unit) and endpoints (e2e).

Channel and Employee reworked: entities, repositories, more abstractions

Oh, I want to make code more prod ready. Better dev experience in future.

Easy start to develop: PostgreSQL on local docker container

Made docker-compose with basic container. To start use script from package.json:

npm run dev:db
npm run prisma:migrate

npm run prisma:reset # use for DB reset

It will up local DB. In .env use for Prisma connect:

DATABASE_URL="postgresql://postgres:postgres@localhost:5432/food?schema=public"

Super easy solution to make e2e tests:

npm run test:e2e

Prisma migration files

Made init SQL.

Full Changelog: v0.1.5...v0.1.6

v0.1.5

countryCode on Channel

On website we want what? Phone validation! For that website should know countryCode, for example 'US'. Ok, now phone input can parse user's value and check if '+1 ' at start was used. For 'RU': check '+7', etc.

SDK reworked

Now there are no methods on parent MainApi(), all entities have own child. This is good for readability. You have to think less.
For example, to get all menu categories in current menu just use: MainApi().menuCategory.listInMenu(menuId)

And...

• 4 new columns for "per 100g": Energy, Protein, Fat, Carbohydrate
• New weight units: ML and L
• MenuCategoryIcon now typed: DEFAULT, BURGER, PIZZA, ROLLS, SUSHI, WOK, CAKE, LASAGNA, DRINK

Go, go!

Full Changelog: v0.1.4...v0.1.5

v0.1.4

Menu category icon changed from url to type: PIZZA, BURGER, etc. 🍕🍔🍰

It’s nice that the category doesn’t have an icon that loads from the installed url. No problems with hosting. Now frontends will be able to have their own icon sets.

All Enums in Prisma Schema was removed 🙈

I didn't appreciate working with enum in PostgreSQL. Huge problems arise when you need to copy data from one database to another. Continue to work with enum will cause a lot of problems in the future. So...

The results of some functions had to be provided with forced types using 'as'. Yes, it's stupid, but tolerable.

• New endpoint: add media to product variant

Full Changelog: v0.1.3...v0.1.4

v0.1.3

Search on Channel now works awesome!

New endpoint: Get popular products.

Of course, many details are not ready. When client search some product and click on url - no changes on DB, as should be.
But already this search is good. Try it live on First frontend

Full Changelog: v0.1.2...v0.1.3

v0.1.2

New endpoint: Search product variants in Channel.

Full Changelog: v0.1.1...v0.1.2

v0.1.1

Checkout: full rework. Some changes on ProductVariant.

Full Changelog: v0.1.0...v0.1.1

v0.1.0

All base business entities are ready. Check main repo: https://github.com/next-orders/v1

Shop

• Media
• Product
• Employee
• Client
• Channel

Channel

• Menu
• ProductVariant
• Checkout

SDK in this repo too. It is used in all related frontends.

Full Changelog: https://github.com/next-orders/api/commits/v0.1.0