Kavya Sharma

same issue tried different tsconfig.json configurations but same issue persists.

Facing the same issue for **'@adminjs/nestjs'** package. Nodejs says **"Cannot find module '@adminjs/nestjs' or its corresponding type declarations.ts(2307)"**. I have properly checked in package.json and node_modules, it has been properly...

> > Facing the same issue for **'@adminjs/nestjs'** package. Nodejs says **"Cannot find module '@adminjs/nestjs' or its corresponding type declarations.ts(2307)"**. I have properly checked in package.json and node_modules, it has...

> Prisma actually uses prepared statements under the hood and also caches and reuses them. > > I hence renamed the issue a tiny bit to make this a request...

Alright, that's nice but still we need a manual prepared statement feature to optimize queries further and remove redundant overhead. Are contributors actively working on this?

A custom plugin could be implemented. ```ts // openapi-ts.config.ts import { UserConfig, defineConfig, DefinePlugin, definePluginConfig, } from "@hey-api/openapi-ts"; type MyEndpointPlugin = DefinePlugin; export const MyEndpointPlugin = definePluginConfig({ config: { omitControllerName:...

> Is there also planned support for accessing custom meta properties when accessing the field through the `useFieldContext` context? Absolutely, if the ordinary field api e.g. ```ts ({ disabled: values.someOtherField...

I am still facing this issue. Here is my form piece. ```ts export const ExtendedUserForm = withForm({ defaultValues: { user: { password: "", username: "" } } as { user?:...