@alevnyacow/nzmt 0.15.13 → 0.15.15
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -2
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -37,7 +37,7 @@ npm i inversify zod reflect-metadata @alevnyacow/nzmt
|
|
|
37
37
|
npx nzmt init prismaClientPath:@/generated/prisma/client
|
|
38
38
|
```
|
|
39
39
|
|
|
40
|
-
After NZMT some basic infrastructure and config file were scaffolded. Open scaffolded file `/server/infrastructure/prisma/client.ts`, then import and set up the necessary Prisma adapter. Now you’re ready to use NZMT!
|
|
40
|
+
After NZMT initialization some basic infrastructure and config file were scaffolded. Open scaffolded file `/server/infrastructure/prisma/client.ts`, then import and set up there the necessary Prisma adapter. Now you’re ready to use NZMT!
|
|
41
41
|
|
|
42
42
|
## Example 1. CRUD for `User` entity with API route handlers and react queries
|
|
43
43
|
|
|
@@ -215,7 +215,7 @@ Command `crud-service` is a lot like the `crud-api` command, but it stops after
|
|
|
215
215
|
- tweak the Product store schemas if needed (`/server/stores/product/product.store.ts`)
|
|
216
216
|
- write Prisma store mappers (`/server/stores/product/product.store.prisma.ts`) as in previous example.
|
|
217
217
|
|
|
218
|
-
`Services` can be used in Server Actions. So, when you make `crud-api`, this generated service can also be used in Server Actions. Using it is very simple, you need `fromDI` function, which was scaffolded when you initialized NMZT. Let's take a look at combined example with two services we've just created:
|
|
218
|
+
`Services` can be used in Server Actions. Well, basically `Stores` can be used too as they are injected the same way as services, but it's strongly recommended to use services. So, when you make `crud-api`, this generated service can also be used in Server Actions. Using it is very simple, you need `fromDI` function, which was scaffolded when you initialized NMZT. Let's take a look at combined example with two services we've just created:
|
|
219
219
|
|
|
220
220
|
```tsx
|
|
221
221
|
'use server'
|