@aklinker1/zeta 1.0.0 → 1.0.2
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 +0 -2
- package/package.json +2 -1
package/README.md
CHANGED
|
@@ -154,8 +154,6 @@ const app = createApp()
|
|
|
154
154
|
|
|
155
155
|
Internally, Zeta uses [`rou3`](https://www.npmjs.com/package/rou3) to match routes. To add a path parameter, you can use `:name`, `**`, or `**:name`. For type safety, you can use a validation framework to define an object schema for the path parameters.
|
|
156
156
|
|
|
157
|
-
|
|
158
|
-
|
|
159
157
|
> Note that path parameters are strings. If your validation framework supports converting strings to other types, like with Zod's [`z.coerce`](https://zod.dev/api?id=coercion) or [`z.stringbool`](https://zod.dev/api?id=stringbool), you can use it to convert the string values to the desired type.
|
|
160
158
|
|
|
161
159
|
### Query Parameters
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@aklinker1/zeta",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.2",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"packageManager": "bun@1.2.17",
|
|
@@ -26,6 +26,7 @@
|
|
|
26
26
|
},
|
|
27
27
|
"scripts": {
|
|
28
28
|
"dev": "bun test --watch",
|
|
29
|
+
"build": "echo 'Noop - nothing to build.'",
|
|
29
30
|
"bench": "bun run src/__tests__/bench.ts",
|
|
30
31
|
"example": "bun --watch run example.ts",
|
|
31
32
|
"example:prod": "NODE_ENV=production bun run example",
|