sinclairzx81
sinclairzx81
Expand below for reference WebCodecs API definitions in lieu of multiple browser support Web Codecs API Definitions ```typescript // ----------------------------------------------------------------------- // MediaStream API: Extension Type Definitions // ----------------------------------------------------------------------- declare interface...
@mcollina Hi! This looks good to me :) @driimus Hey, good work on these PR's and great to see the topic of contravariance overviewed in the Type Provider implementer documentation....
@driimus @mcollina Hi. This is a good find! I think it would be ok to update the existing providers to have them infer as `unknown` (instead of `never`) if it...
@driimus Hey, awesome :) Not too sure the best convention for updating across multiple Fastify packages (it's probably better to get some inputs from @fastify/typescript contributors on matters of logistics;...
Hi, I'd actually really like to support this, however terminals with VT340 emulation support seem to be a bit few and far between (at least for what I've been able...
@zekth Hi. Just had a look at the type definitions and they look ok to me, however removing `void` for the callback return type would disallow the following implementation. ```typescript...
@RafaelGSS Just had a bit of a deeper look at this. From the original issue https://github.com/fastify/fastify-type-provider-typebox/issues/2#issue-1105737990, the user is reporting a problem registering plugin where both instance and plugin are...
@rubenferreira97 Try the following ```typescript import Fastify, { ContextConfigDefault, FastifySchema, preValidationAsyncHookHandler, RawReplyDefaultExpression, RawRequestDefaultExpression, RawServerDefault, FastifyTypeProvider } from 'fastify'; import { TypeBoxTypeProvider } from '@fastify/type-provider-typebox'; import { Type } from '@sinclair/typebox';...
@rubenferreira97 That's ok. And yeah you're quite right that if you do need to share the same hook across different routes, constraining to one set of schemas will be a...
@rubenferreira97 Hi, Type Providers are written to infer types from JS values (as opposed to explicit generics). Internally the resolver infrastructure checks the value of the user supplied object schema...