Skip to content

Releases: samchon/typia

v9.1.1

10 Apr 04:39
535260f
Compare
Choose a tag to compare

What's Changed

Full Changelog: 9.1.0...v9.1.1

9.1.0

08 Apr 07:10
75dcc07
Compare
Choose a tag to compare

What's Changed

  • Bump the ecosystem group across 1 directory with 3 updates by @dependabot in #1565
  • Bump typescript from 5.8.2 to 5.8.3 in /test in the ecosystem group by @dependabot in #1566
  • New function typia.json.schema<T>() by @samchon in #1567

Full Changelog: v9.0.1...9.1.0

v9.0.1

05 Apr 20:04
aeec9cc
Compare
Choose a tag to compare

Major update from @samchon/openapi: https://github.com/samchon/openapi/releases/tag/v4.0.0

export namespace JsonSchema {
  export interface INumber {
    type: "number";
    minimum?: number;
    maximum?: number;
    exclusiveMinimum?: number; // boolean -> number
    exclusiveMaximum?: number; // boolean -> number;
    examples?: Record<string, any> | Array<any>; // object -> array | object
  }
}

Anthropic Claude has banned boolean typed exclusiveMinimum and exclusiveMaximum properties. So @samchon/openapi has changed them to number type to support Anthropic Claude perflectly, and it is a typical major update taking a break change on types.

Also, in the JSON schema specifications, examples property has been changed from Array<any> type to Record<string, any> type since OpenAPI v3 update. However, too much people and frameworks are not responding such specification change. So, many of users validating OpenAPI specification by typia.assert<OpenApiV3_1.IDocument>(doc) function had been failed due to such JsonSchema.examples reason.

@samchon/openapi's new release allows non-standard example type (Array<any>) considering the industrial environments, and supports polyfill methods instead.

To respond such break changes with major update from @samchon/openapi, typia has released new major update v9. Also, realising a new major update, typia has enhanced number & tags.Type<"uint32"> like unsigned integer type about JSON schema generation. From now on, when define a number & tags.Type<"int32"> like tag, it would also contain the minimum: 0 constraint in the JSON schema.

What's Changed

  • exclusiveMinimum/exclusiveMaximum as number type by @samchon in #1562
  • Enhance uint type's JSON schema property. by @samchon in #1563
  • Fix comment tag written @exclusiveMinimum case. by @samchon in #1564

Full Changelog: v8.2.0...v9.0.1

v8.2.0

04 Apr 16:06
ec86821
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v8.1.1...v8.2.0

v8.1.1

30 Mar 15:01
c06c696
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v8.1.0...v8.1.1

v8.1.0

29 Mar 10:44
a4dff83
Compare
Choose a tag to compare

What's Changed

Full Changelog: v8.0.4...v8.1.0

v8.0.4

26 Mar 16:11
9a23470
Compare
Choose a tag to compare

What's Changed

Full Changelog: v8.0.3...v8.0.4

v8.0.3

16 Mar 16:28
8f4413b
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v8.0.2...v8.0.3

v8.0.2

14 Mar 16:40
1e80d3f
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v8.0.1...v8.0.2

v8.0.1

11 Mar 12:51
65d0fbc
Compare
Choose a tag to compare

What's Changed

Full Changelog: v8.0.0...v8.0.1