tsoa-next 8.2.0-dev.63.a32e6e22 → 8.2.1-dev.65.5d3e3033

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.
Files changed (2) hide show
  1. package/README.MD +3 -3
  2. package/package.json +3 -3
package/README.MD CHANGED
@@ -28,7 +28,7 @@ Where historical release notes or migration references still point upstream, the
28
28
  ## Goal
29
29
 
30
30
  - TypeScript controllers and models as the single source of truth for your API
31
- - A valid OpenAPI (formerly Swagger) spec (2.0 or 3.0 if you choose 😍) is generated from your controllers and models, including:
31
+ - A valid OpenAPI (formerly Swagger) 2.0, 3.0, or 3.1 spec is generated from your controllers and models, including:
32
32
  - Paths (e.g. GET /users)
33
33
  - Definitions based on TypeScript interfaces (models)
34
34
  - Parameters/model properties marked as required or optional based on TypeScript (e.g. myProperty?: string is optional in the OpenAPI spec)
@@ -44,8 +44,8 @@ Where historical release notes or migration references still point upstream, the
44
44
  - Use jsdoc for pure text metadata (e.g. endpoint descriptions)
45
45
  - Minimize boilerplate
46
46
  - Models are best represented by interfaces (pure data structures), but can also be represented by classes
47
- - Runtime validation of tsoa-next should behave as closely as possible to the specifications that the generated OpenAPI 2/3 schema describes. Any differences in validation logic are clarified by logging warnings during the generation of the OpenAPI Specification (OAS) and/or the routes.
48
- - Please note that by enabling OpenAPI 3 you minimize the chances of divergent validation logic since OpenAPI 3 has a more expressive schema syntax.
47
+ - Runtime validation of tsoa-next should behave as closely as possible to the specifications that the generated OpenAPI schema describes. Any differences in validation logic are clarified by logging warnings during the generation of the OpenAPI Specification (OAS) and/or the routes.
48
+ - Please note that by enabling OpenAPI 3.0 or 3.1 you minimize the chances of divergent validation logic since the newer schema shapes are more expressive than OpenAPI 2.0.
49
49
 
50
50
  ## Feature List
51
51
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "tsoa-next",
3
- "version": "8.2.0-dev.63.a32e6e22",
3
+ "version": "8.2.1-dev.65.5d3e3033",
4
4
  "description": "Build swagger-compliant REST APIs using TypeScript and Node",
5
5
  "main": "./dist/index.js",
6
6
  "typings": "./dist/index.d.ts",
@@ -32,8 +32,8 @@
32
32
  "author": "Vanna DiCatania <vanna@dicatania.me> (http://www.dicatania.me)",
33
33
  "license": "MIT",
34
34
  "dependencies": {
35
- "@tsoa-next/cli": "8.2.0-dev.63.a32e6e22",
36
- "@tsoa-next/runtime": "8.2.0-dev.63.a32e6e22"
35
+ "@tsoa-next/cli": "8.2.1-dev.65.5d3e3033",
36
+ "@tsoa-next/runtime": "8.2.1-dev.65.5d3e3033"
37
37
  },
38
38
  "devDependencies": {
39
39
  "@types/node": "24.12.0",