typespec-http-zod 0.7.0 → 0.8.0

package/dist/src/api.js

@@ -1046,7 +1046,22 @@ function renderSchemas(registry, externals, routeDeclarations, runtimeModule) {
         const annotation = d.annotated === true ? `: z.ZodType<${d.typeName}>` : "";
         return `\n${declared}\nexport const ${d.identifier}${annotation} = ${d.source};\n`;
     });
-    const parts = [GENERATED_BANNER, '\nimport { z } from "zod";\n'];
+    /**
+     * **Written only when something in the file names it**, like the `ResponseArm` import below and for
+     * the same reason: an unused import fails the lint a generated file has to pass like any other.
+     *
+     * `z` is reached through a declaration's source or a route's arms, so a service whose every
+     * operation takes nothing and returns `void` declares neither and named it never:
+     * `TS6133: 'z' is declared but its value is never read`, from a compile that reported success. Two
+     * bare `GET`s is where a health check starts, so it is where a new consumer starts.
+     *
+     * Decided from the declarations rather than by searching the rendered text, which is the mistake
+     * this file has made four times.
+     */
+    const usesZod = declarations.length > 0 || routeDeclarations.length > 0;
+    const parts = [GENERATED_BANNER];
+    if (usesZod)
+        parts.push('\nimport { z } from "zod";\n');
     /**
      * A TYPE import, so nothing of this package's survives into the emitted JavaScript.
      *

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "typespec-http-zod",
-  "version": "0.7.0",
+  "version": "0.8.0",
   "description": "TypeSpec emitter and library: turn an HTTP service definition into Zod validators and framework-free contract types that agree, keyword for keyword, with the OpenAPI document @typespec/openapi3 publishes from the same source.",
   "keywords": [
     "codegen",