-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom column type update - BRA-1935 #549
base: main
Are you sure you want to change the base?
Conversation
… into tara/bra-1935
… into tara/bra-1935
… into tara/bra-1935
core/js/typespecs/app_types.ts
Outdated
@@ -177,12 +177,18 @@ const customColumnBaseSchema = generateBaseTableSchema("custom columns"); | |||
export const customColumnSchema = z | |||
.object({ | |||
id: customColumnBaseSchema.shape.id, | |||
object_type: aclObjectTypeEnum, | |||
object_type: z |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if we should actually leave these as-is, and just use a less-permissive version of the schema on the API side. The benefit being that control-plane-side (which is always in sync with the latest typespecs) we still get the stricter typing benefits, but data-plane-side we decay these to strings. Not a terribly strong opinion here, so either way works.
… into tara/bra-1935
… into tara/bra-1935
… into tara/bra-1935
… into tara/bra-1935
… into tara/bra-1935
Update custom column type