@dudousxd/nestjs-codegen 0.17.1 → 0.18.0

package/CHANGELOG.md

@@ -1,5 +1,53 @@
 # @dudousxd/nestjs-codegen
 
+## 0.18.0
+
+### Minor Changes
+
+- 553e503: Resolve the entity of a controller factory called with a single options object.
+
+  `class X extends createTableController({ entity: Util, dto: UtilDTO })` emitted
+  every one of its routes with `body: never` and `filterFields: never` — the typed
+  filter builder gone from the client, with `tsc` and codegen both green. Only the
+  positional form (`createTableController(Util, { dto })`) worked: discovery
+  collected call-site classes by scanning for identifier ARGUMENTS, and an object
+  literal is not one, so the entity behind the factory's generated
+  `@Filterable({ entity })` was unresolvable. Measured downstream at 22 tables
+  losing their filter builder at once.
+
+  Class-valued properties of an options-object argument are now collected too,
+  keyed by property name, and the entity resolver prefers a named `entity` over the
+  first positional argument. Both call forms work, so a codebase can migrate table
+  by table.
+
+  `MixinBinding` gains `namedClassArgs: Record<string, { name, filePath }>`
+  alongside the unchanged positional `classArgs`. The key is what identifies an
+  argument's role once there is no positional order to read it from, and consumers
+  want different properties: this package resolves `entity`, while
+  `@dudousxd/nestjs-filter-codegen` reads `filter` off the same binding.
+
+## 0.17.2
+
+### Patch Changes
+
+- fcf816e: Resolve `@ApplyFilter(<Table>.filter)` on overridden mixin routes.
+
+  A controller that extends a factory-produced base and overrides one of its
+  routes has to re-declare `@ApplyFilter`, and the only handle on the filter the
+  factory generated internally is the static it hands back — a property access,
+  not an importable identifier. Discovery accepted identifiers only, so it skipped
+  the decorator entirely.
+
+  The failure was silent and total rather than partial: the route emitted with
+  `body: never` and `filterFields: never`, dropping the typed filter builder from
+  exactly the routes that took the override escape hatch, while `tsc` and codegen
+  both stayed green. It only surfaced downstream, as a client call that could no
+  longer be typed.
+
+  Such a property access is now resolved through the factory — const → factory
+  call → returned class → static property → the class declared in the factory
+  body.
+
 ## 0.17.1
 
 ### Patch Changes