Juan Villa

Hey @steve-chavez , thanks for the awesome update. Once Supabase users can upgrade their version of Postgrest, will that be enough to start using the supabase client to order by...

I too was able to bypass the issue with this bug by wrapping my values call with sql``: ```TypeScript const product = await tx .insert(products) .values({ entityId: input.entityId, eventType: input.eventType,...

This would be amazing!

Yeah, this would be amazing. I don't see any use case for having the generated columns there. They shouldn't even be queryable by the Supabase Client IMO.

Any chance anyone's actively looking at adding indexed (GIN or GIST)generated ts_vector columns? This is one of the last things that will let us move away from Supabase and over...

This is likely related to the [issue](https://github.com/drizzle-team/drizzle-orm/issues/1185) I created. When we set mode to string, TypeScript shows the return type as string, however a date object is returned. I suspect...

Pretty sure this is caused by us calling setFieldValue directly on the constructor of FieldApi here: https://github.com/TanStack/form/blob/72b4572ed644f6699eacb186fdd6c2f536c73219/packages/form-core/src/FieldApi.ts#L999-L1002 When you defined a defaultValue, and the component is rendering, within the same...

Update: a simple workaround right now is to not conditionally render the whole form.Field, but rather just content within the children. This way we ensure the Field is initiated despite...

@asegarra has this been resolved for you in latest?

Added type and runtime tests, especially focused on making sure the errors object is still being properly inferred when any combo of form/field validations are used. Additionally, originally I wanted...