build(deps-dev): bump @sinclair/typebox from 0.24.51 to 0.25.24

[dependabot]

Bumps @sinclair/typebox from 0.24.51 to 0.25.24.

Changelog

Sourced from @​sinclair/typebox's changelog.

0.25.24

Updates:

• 331 Implements an additional check specific to property types of required & undefined. This to ensure the property key exists when the property value extends undefined.
• 331 Documentation updates for Ajv and TypeCompiler

Additional:

• 331 Remove unusued recursive code paths for create and cast.

0.25.23

Updates:

• 324 TypeScript Language Service now presents JSDoc comments when inferring static object properties. (IntelliSense)
• 325 Additional property inference optimizations.

Additional:

• Huge thank you to Github user stevezhu for these excellent contributions.

0.25.22

Updates:

• 323 adds compiler support for UTF-16 (unicode) characters for schema identifiers.

0.25.18

Updates:

• 307 implements date conversion when casting values with Value.Cast(Type.Date(), ...). Castable values include numbers (interpretted as timestamps) and iso8601 string values. Uncastable values will result in dates with values of 1970-01-01T00:00:00.000Z. This version also includes more robust checks for Dates initialized with invalid values.

0.25.11

Updates:

• 286 implements a FNV1A-64 non cryptographic hashing function in TypeBox. This function should not be used in place of cryptographic hashing functions, rather it's purpose is to provide relatively fast, hashing mechanism to assist with checks for arrays with uniqueItems constraints, specifically for cases where the array may contains reference values (such as objects, arrays, Dates and Uint8Array). This function is provided via Value.Hash() for convenience as the hash may be useful to generate a numeric identifier for values (with some considerations to React array rendering in absence of key or identifier)

0.25.10

Updates:

• 283 Updates the custom type validator callback signature to accept a schema instance. The schema instance may include additional constraints (such as options) that may be used during the validation process. Custom.Set('<Kind>', (schema, value) => { ... }).

0.25.9

Updates:

... (truncated)

Commits

• 078cfac Support Required Undefined Property Check (#331)
• 5a520a1 Documentation
• 1159041 TRPC Documentation (#326)
• fb5fabf ReadonlyObject Extension
• ac0a3e2 Update Example
• 5515fb6 Property Inference Optimization (#325)
• 13682f6 Support JSDoc IntelliSense on Object Properties (#324)
• 14b4d4a Support UTF-16 Identifiers (#323)
• c4061c1 Annual License Update (#312)
• a57f858 Use Relative Import
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[changeset-bot]

⚠️ No Changeset found

Latest commit: 73d0009

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR