[Snyk] Upgrade typia from 6.3.1 to 9.3.1 #3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Snyk has created this PR to upgrade typia from 6.3.1 to 9.3.1.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 209 versions ahead of your current version.
The recommended version was released 22 days ago.
Release notes
Package name: typia
What's Changed
@ samchon/openapi
for deprecation reason by @ samchon in #1584Full Changelog: v9.3.0...v9.3.1
What's Changed
typia.llm.controller<Class, Model>()
. by @ samchon in #1582Full Changelog: v9.2.0...v9.3.0
Started supporting
standard-schema
fromtypia.createValidate<T>()
function.What's Changed
@ samchon/openapi
only inpnpm-lock.yaml
by @ samchon in #1570unplugin-typia
,npm
instead ofjsr
by @ samchon in #1579New Contributors
Full Changelog: v9.1.1...v9.2.0
What's Changed
@ types/node
by @ samchon in #1569Full Changelog: 9.1.0...v9.1.1
What's Changed
typia.json.schema<T>()
by @ samchon in #1567Full Changelog: v9.0.1...9.1.0
Major update from
@ samchon/openapi
: https://github.com/samchon/openapi/releases/tag/v4.0.0Anthropic Claude has banned
boolean
typedexclusiveMinimum
andexclusiveMaximum
properties. So@ samchon/openapi
has changed them tonumber
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 fromArray<any>
type toRecord<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 bytypia.assert<OpenApiV3_1.IDocument>(doc)
function had been failed due to suchJsonSchema.examples
reason.@ samchon/openapi
's new release allows non-standardexample
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 enhancednumber & tags.Type<"uint32">
like unsigned integer type about JSON schema generation. From now on, when define anumber & tags.Type<"int32">
like tag, it would also contain theminimum: 0
constraint in the JSON schema.What's Changed
exclusiveMinimum
/exclusiveMaximum
asnumber
type by @ samchon in #1562uint
type's JSON schema property. by @ samchon in #1563@ exclusiveMinimum
case. by @ samchon in #1564Full Changelog: v8.2.0...v9.0.1
What's Changed
New Contributors
Full Changelog: v8.1.1...v8.2.0
What's Changed
typia generate
by @ sushichan044 in #1557New Contributors
Full Changelog: v8.1.0...v8.1.1
What's Changed
@ samchon/openapi
by @ samchon in #1556Full Changelog: v8.0.4...v8.1.0
What's Changed
Full Changelog: v8.0.3...v8.0.4
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information: