@valbuild/shared 0.76.0 → 0.76.1

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.
@@ -1105,7 +1105,8 @@ var FileOperation = function FileOperation(path) {
1105
1105
  op: zod.z.literal("file"),
1106
1106
  path: path,
1107
1107
  filePath: zod.z.string(),
1108
- value: zod.z.string(),
1108
+ value: JSONValueT,
1109
+ // TODO: this should be string, but we believe we have a bug in Zod where setting this to z.string(), means that other types of patches also ends up requiring a string after we deploy a version
1109
1110
  remote: zod.z["boolean"](),
1110
1111
  nestedFilePath: zod.z.array(zod.z.string()).optional(),
1111
1112
  metadata: JSONValueT.optional() // TODO: remove optional
@@ -2174,7 +2175,9 @@ var createValClient = function createValClient(host, config // We want to use th
2174
2175
  _context2.next = 11;
2175
2176
  break;
2176
2177
  }
2177
- console.error("Invalid request body", {
2178
+ console.error("Got an invalid request body while validating client-side. This is most likely a Val bug.", {
2179
+ path: path,
2180
+ method: method,
2178
2181
  body: anyReq.body,
2179
2182
  error: reqBodyResult.error
2180
2183
  });
@@ -1105,7 +1105,8 @@ var FileOperation = function FileOperation(path) {
1105
1105
  op: zod.z.literal("file"),
1106
1106
  path: path,
1107
1107
  filePath: zod.z.string(),
1108
- value: zod.z.string(),
1108
+ value: JSONValueT,
1109
+ // TODO: this should be string, but we believe we have a bug in Zod where setting this to z.string(), means that other types of patches also ends up requiring a string after we deploy a version
1109
1110
  remote: zod.z["boolean"](),
1110
1111
  nestedFilePath: zod.z.array(zod.z.string()).optional(),
1111
1112
  metadata: JSONValueT.optional() // TODO: remove optional
@@ -2174,7 +2175,9 @@ var createValClient = function createValClient(host, config // We want to use th
2174
2175
  _context2.next = 11;
2175
2176
  break;
2176
2177
  }
2177
- console.error("Invalid request body", {
2178
+ console.error("Got an invalid request body while validating client-side. This is most likely a Val bug.", {
2179
+ path: path,
2180
+ method: method,
2178
2181
  body: anyReq.body,
2179
2182
  error: reqBodyResult.error
2180
2183
  });
@@ -1101,7 +1101,8 @@ var FileOperation = function FileOperation(path) {
1101
1101
  op: z.literal("file"),
1102
1102
  path: path,
1103
1103
  filePath: z.string(),
1104
- value: z.string(),
1104
+ value: JSONValueT,
1105
+ // TODO: this should be string, but we believe we have a bug in Zod where setting this to z.string(), means that other types of patches also ends up requiring a string after we deploy a version
1105
1106
  remote: z["boolean"](),
1106
1107
  nestedFilePath: z.array(z.string()).optional(),
1107
1108
  metadata: JSONValueT.optional() // TODO: remove optional
@@ -2170,7 +2171,9 @@ var createValClient = function createValClient(host, config // We want to use th
2170
2171
  _context2.next = 11;
2171
2172
  break;
2172
2173
  }
2173
- console.error("Invalid request body", {
2174
+ console.error("Got an invalid request body while validating client-side. This is most likely a Val bug.", {
2175
+ path: path,
2176
+ method: method,
2174
2177
  body: anyReq.body,
2175
2178
  error: reqBodyResult.error
2176
2179
  });
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@valbuild/shared",
3
- "version": "0.76.0",
3
+ "version": "0.76.1",
4
4
  "private": false,
5
5
  "description": "Val shared types and utilities",
6
6
  "scripts": {
@@ -29,7 +29,7 @@
29
29
  "exports": true
30
30
  },
31
31
  "dependencies": {
32
- "@valbuild/core": "~0.76.0",
32
+ "@valbuild/core": "~0.76.1",
33
33
  "zod": "^3.22.4",
34
34
  "zod-validation-error": "^3.3.0"
35
35
  },