Marcel Overdijk

I'm experiencing the same issue. Is there maybe a workaround until it's supported? Here is also a [blog](https://spring.io/blog/2025/03/10/null-safety-in-spring-apps-with-jspecify-and-null-away) post about Spring Framework moving to JSpecify. So wider adoption of these...

Just to explain more. On the configuration page there is a link to go to the next section: (Showcase)  On that Showcase page there is a link to the...

Hi @rruggiero I was thinking about this in the past as well, but in a more simple approach. Just adding a verwoon table with a single row/column indicating the current...

Hi @robert1508 is there a rough timeline for it?

You could use `coerce`: ``` export const PetIdRequestParamSchema = z.object({ petId: z.coerce .number() .int() .openapi({ param: { name: 'petId', in: 'path', }, description: 'The pet identifier.', example: 123, }), });...

hi @stabildev I must admit I found some issue with my suggested approach as well yesterday evening. The earlier mentioned code: ``` export const PetIdRequestParamSchema = z.object({ petId: z.coerce .number()...

I'm also using VC Code, but my chain is different. I'm using Prisma.

OK np, do you have other suggestions? Or is it recommended users should simply use `c.text('my message', 404)` or `c.json({ .. }, 404)` when a custom text / json response...

I think passing the `filters` object would already help a lot: ``` let filters = await this.getFilters(); ... return { success: true, result: this.meta.model.serializer(obj, filters), }; ```

See https://github.com/honojs/middleware/issues/323