@nxgt/typespec 0.13.1 → 0.13.2

package/README.md

@@ -339,7 +339,8 @@ model Place {
 Each is an OpenAPI component named as in GraphQL (`Latitude`, `URL`), with a
 `format`, a pattern or bounds approximating the rule, and `x-nxgt-scalar`
 naming it. The exact rules (checksums, ISO and IANA lists) are outside the
-pattern. TypeSpec's own `url` takes any scheme; `httpUrl` takes `http:` and
+pattern; [`@nxgt/openapi-codegen`](https://github.com/softistx/nxgt-http/blob/develop/packages/openapi-codegen/docs/guide/options.md#scalars)'s
+`scalars: 'exact'` checks them with the schemas of `@nxgt/zod`. TypeSpec's own `url` takes any scheme; `httpUrl` takes `http:` and
 `https:`. Every scalar by category, in
 [Scalars](docs/guide/scalars.md); the ids, the addresses and the columns, in
 [Scalars and columns](docs/guide/columns.md).

package/docs/guide/scalars.md

@@ -67,9 +67,12 @@ components:
 | `description` | The rule in words, and what the pattern leaves out. |
 
 A generator that knows nothing of `x-nxgt-scalar` still validates the pattern
-and the bounds. A later `@nxgt/openapi-codegen` release will map it to the exact
-Zod schema from `@nxgt/zod` ([roadmap](../roadmap.md)); until then, what a
-scalar leaves out is not checked.
+and the bounds. `@nxgt/openapi-codegen` with
+[`scalars: 'exact'`](https://github.com/softistx/nxgt-http/blob/develop/packages/openapi-codegen/docs/guide/options.md#scalars) maps it to the exact Zod
+schema from `@nxgt/zod`, the checksum, the list or the `Intl` rule included;
+with the default `'pattern'`, what a scalar leaves out is not checked. The
+codecs (`dateTime`, `timestamp`, `bigInt`, `long`) keep their pattern under
+`'exact'` too.
 
 ## Names
 

package/docs/roadmap.md

@@ -10,9 +10,7 @@ Nothing in progress.
 
 ## Next
 
-- **Exact scalar rules in the generated code.** `@nxgt/openapi-codegen` maps
-  `x-nxgt-scalar` to the exact Zod schema from `@nxgt/zod`: the checksums,
-  the ISO and IANA lists and the `Intl` rules the patterns leave out.
+Nothing planned beyond what is under Later.
 
 ## Later
 
@@ -27,6 +25,15 @@ Nothing in progress.
 
 ## Shipped
 
+### 0.13.2
+
+- **Exact scalar rules in the generated code.** `@nxgt/openapi-codegen`
+  with `scalars: 'exact'` maps `x-nxgt-scalar` to the exact Zod schema from
+  `@nxgt/zod`: the checksums, the ISO and IANA lists, the `Intl` rules and the
+  refusal of `-0` the patterns leave out. The codecs keep their pattern until
+  `@nxgt/zod` offers their wire schemas. The guides and the troubleshooting
+  entries say so.
+
 ### 0.13.0
 
 - **The emitter `@nxgt/typespec`.** `emit: ["@nxgt/typespec"]` runs

package/docs/troubleshooting.md

@@ -628,12 +628,17 @@ one.
 
 **Why:** the scalar's pattern checks the shape. A list (`countryCode`,
 `currency`, `timeZone`, `locale`) or a checksum (`iban`, ISBN) does not fit in
-a pattern. `x-nxgt-scalar` names the exact rule, but `@nxgt/openapi-codegen`
-does not map it to the `@nxgt/zod` schema yet ([roadmap](roadmap.md)).
-
-**Fix:** until it does, check the value in the handler against the exact
-rule, the list or the checksum, from `@nxgt/zod` or your own table, and answer
-`400` as the generated validator does:
+a pattern. `x-nxgt-scalar` names the exact rule, and `@nxgt/openapi-codegen`
+maps it to the `@nxgt/zod` schema only with `scalars: 'exact'`; the default is
+`'pattern'`.
+
+**Fix:** generate with
+[`scalars: 'exact'`](https://github.com/softistx/nxgt-http/blob/develop/packages/openapi-codegen/docs/guide/options.md#scalars)
+(`bun add @nxgt/zod`, then `generate({ …, scalars: 'exact' })`): `iban` is
+checked by `ibanSchema`, `countryCode` by its list of assigned codes. If you
+cannot, check the value in the handler against the exact rule, the list or the
+checksum, from `@nxgt/zod` or your own table, and answer `400` as the generated
+validator does:
 
 ```ts
 if (!knownCountries.has(body.country)) {
@@ -651,7 +656,8 @@ where `@nxgt/graphql-scalars` refuses it.
 tell from `0`. For `nonNegativeInt`, `nonPositiveInt`, `port`, the bound holds,
 so the value passes (`positiveInt` and `negativeInt` refuse it by their bound).
 
-**Fix:** normalise in the handler when the sign matters:
+**Fix:** generate with [`scalars: 'exact'`](https://github.com/softistx/nxgt-http/blob/develop/packages/openapi-codegen/docs/guide/options.md#scalars), whose schemas refuse `-0` for
+an integer scalar. Otherwise normalise in the handler when the sign matters:
 
 ```ts
 const quantity = Object.is(body.quantity, -0) ? 0 : body.quantity;

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@nxgt/typespec",
-	"version": "0.13.1",
+	"version": "0.13.2",
 	"license": "MIT",
 	"type": "module",
 	"main": "./dist/index.js",
@@ -61,8 +61,9 @@
 		}
 	},
 	"devDependencies": {
-		"@nxgt/openapi-codegen": "^0.9.2",
+		"@nxgt/openapi-codegen": "^0.10.0",
 		"@nxgt/openapi-hono": "^0.3.3",
+		"@nxgt/zod": "^0.1.3",
 		"@types/bun": "^1.4.0",
 		"@typespec/compiler": "1.17.0",
 		"@typespec/http": "1.17.0",