@nestia/core 3.16.0-dev.20240926 → 3.17.0-dev.20240928

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.
@@ -85,9 +85,9 @@ export declare namespace EncryptedRoute {
85
85
  * instead of throwing the 400 bad request error.
86
86
  *
87
87
  * By the way, be careful. If you've configured the response
88
- * transformation option to be `validate.log` or `validateEquals.log`,
89
- * client may get wrong response data. Therefore, this way is not
90
- * recommended in the common backend server case.
88
+ * transformation option to be `validate.log`, client may get wrong
89
+ * response data. Therefore, this way is not recommended in the common
90
+ * backend server case.
91
91
  *
92
92
  * @param func Logger function
93
93
  * @default console.log
@@ -80,9 +80,9 @@ var EncryptedRoute;
80
80
  * instead of throwing the 400 bad request error.
81
81
  *
82
82
  * By the way, be careful. If you've configured the response
83
- * transformation option to be `validate.log` or `validateEquals.log`,
84
- * client may get wrong response data. Therefore, this way is not
85
- * recommended in the common backend server case.
83
+ * transformation option to be `validate.log`, client may get wrong
84
+ * response data. Therefore, this way is not recommended in the common
85
+ * backend server case.
86
86
  *
87
87
  * @param func Logger function
88
88
  * @default console.log
@@ -80,9 +80,9 @@ export declare namespace TypedRoute {
80
80
  * instead of throwing the 400 bad request error.
81
81
  *
82
82
  * By the way, be careful. If you've configured the response
83
- * transformation option to be `validate.log` or `validateEquals.log`,
84
- * client may get wrong response data. Therefore, this way is not
85
- * recommendedin the common backend server case.
83
+ * transformation option to be `validate.log`, client may get wrong
84
+ * response data. Therefore, this way is not recommended in the common
85
+ * backend server case.
86
86
  *
87
87
  * @param func Logger function
88
88
  * @default console.log
@@ -70,9 +70,9 @@ var TypedRoute;
70
70
  * instead of throwing the 400 bad request error.
71
71
  *
72
72
  * By the way, be careful. If you've configured the response
73
- * transformation option to be `validate.log` or `validateEquals.log`,
74
- * client may get wrong response data. Therefore, this way is not
75
- * recommendedin the common backend server case.
73
+ * transformation option to be `validate.log`, client may get wrong
74
+ * response data. Therefore, this way is not recommended in the common
75
+ * backend server case.
76
76
  *
77
77
  * @param func Logger function
78
78
  * @default console.log
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@nestia/core",
3
- "version": "3.16.0-dev.20240926",
3
+ "version": "3.17.0-dev.20240928",
4
4
  "description": "Super-fast validation decorators of NestJS",
5
5
  "main": "lib/index.js",
6
6
  "typings": "lib/index.d.ts",
@@ -36,7 +36,7 @@
36
36
  },
37
37
  "homepage": "https://nestia.io",
38
38
  "dependencies": {
39
- "@nestia/fetcher": "^3.16.0-dev.20240926",
39
+ "@nestia/fetcher": "^3.17.0-dev.20240928",
40
40
  "@nestjs/common": ">=7.0.1",
41
41
  "@nestjs/core": ">=7.0.1",
42
42
  "@samchon/openapi": "^1.1.0",
@@ -53,7 +53,7 @@
53
53
  "ws": "^7.5.3"
54
54
  },
55
55
  "peerDependencies": {
56
- "@nestia/fetcher": ">=3.16.0-dev.20240926",
56
+ "@nestia/fetcher": ">=3.17.0-dev.20240928",
57
57
  "@nestjs/common": ">=7.0.1",
58
58
  "@nestjs/core": ">=7.0.1",
59
59
  "reflect-metadata": ">=0.1.12",
@@ -95,9 +95,9 @@ export namespace EncryptedRoute {
95
95
  * instead of throwing the 400 bad request error.
96
96
  *
97
97
  * By the way, be careful. If you've configured the response
98
- * transformation option to be `validate.log` or `validateEquals.log`,
99
- * client may get wrong response data. Therefore, this way is not
100
- * recommended in the common backend server case.
98
+ * transformation option to be `validate.log`, client may get wrong
99
+ * response data. Therefore, this way is not recommended in the common
100
+ * backend server case.
101
101
  *
102
102
  * @param func Logger function
103
103
  * @default console.log
@@ -84,9 +84,9 @@ export namespace TypedRoute {
84
84
  * instead of throwing the 400 bad request error.
85
85
  *
86
86
  * By the way, be careful. If you've configured the response
87
- * transformation option to be `validate.log` or `validateEquals.log`,
88
- * client may get wrong response data. Therefore, this way is not
89
- * recommendedin the common backend server case.
87
+ * transformation option to be `validate.log`, client may get wrong
88
+ * response data. Therefore, this way is not recommended in the common
89
+ * backend server case.
90
90
  *
91
91
  * @param func Logger function
92
92
  * @default console.log