nickluger

Does anybody have a simple workaround for this? We are currently forced to do some TS generic wrapping everywhere we return something from Prisma, as the `select` fields might change,...

Could reproduce this. Exactly as said. If, for example, you have two menus (like in the image), **tapping** their menu buttons directly after each other will lead to both menus...

Pretty contrived Workaround: The only reference to manually closing the menu i found in the docs is this: https://headlessui.com/react/menu#closing-menus-manually. (It seems there's no controlled version of this component) So you...

This is a ~~working workaround~~: ```ts import type { V2_ServerRuntimeMetaArgs, V2_ServerRuntimeMetaDescriptor, } from "@remix-run/server-runtime"; import type { UseDataFunctionReturn } from "remix-typedjson"; export type V2TypedMetaFunction = ( args: Omit & {...

Is this fixed? I seem to be able to generate tokens with `exp` set correctly.

There should be a fat warning on the React doc, before people waste their time implementing everything just to find out they can only `git reset --hard` an hour later...

There is [`@@ignore`](https://www.prisma.io/docs/reference/api-reference/prisma-schema-reference#ignore-1), but I think it affects only exclusion from the client, and not the migration process. Sometimes other systems control the migration process for certain tables, so it...

This works for Postgres (>=12), but it should work similarly for other RDBMS: In general, you need two database users/roles (synonym in Postgres for our purposes). Let's call them `prisma`...

Brief addendum for ppl landing here from Google, and also my future self (landing here from Google): Of course, you need to make sure that the `prisma` role does **not...