@alevnyacow/nzmt 0.22.4 → 0.22.6
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
|
@@ -219,7 +219,7 @@ This method can be used directly as a Next.js API route handler. If you examine
|
|
|
219
219
|
```ts
|
|
220
220
|
// api/user-controller/route.ts
|
|
221
221
|
import { fromDI } from '@/server/di'
|
|
222
|
-
import type { UserController } from '@/server/controllers'
|
|
222
|
+
import type { UserController } from '@/server/controllers/user'
|
|
223
223
|
|
|
224
224
|
const controller = fromDI<UserController>('UserController')
|
|
225
225
|
|
|
@@ -242,7 +242,7 @@ The behavior of all server modules in NZMT is governed by Zod schemas. Function
|
|
|
242
242
|
|
|
243
243
|
## Can I tweak scaffolded files?
|
|
244
244
|
|
|
245
|
-
Yes — everything is fully editable, including configuration. Think of NZMT as a shadcn-style approach for full-stack: scaffold first, then fully own the code. Moreover, in most of the cases your changes are preserved on subsequent generations. For example, if you modify a generated query and
|
|
245
|
+
Yes — everything is fully editable, including configuration. Think of NZMT as a shadcn-style approach for full-stack: scaffold first, then fully own the code. Moreover, in most of the cases your changes are preserved on subsequent generations. For example, if you modify a generated query and run `npx nzmt rq` later, your edits stay intact.
|
|
246
246
|
|
|
247
247
|
## Do I really need to understand DI and other fancy concepts to use NZMT?
|
|
248
248
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@alevnyacow/nzmt",
|
|
3
|
-
"version": "0.22.
|
|
3
|
+
"version": "0.22.6",
|
|
4
4
|
"description": "Next Zod Modules Toolkit",
|
|
5
5
|
"keywords": ["next", "full-stack", "server", "backend", "cli", "scaffolder", "zod", "rest", "contract programming", "react-query", "ddd", "domain-driven"],
|
|
6
6
|
"repository": {
|