nemophrost Comments - Convex Community

After some further investigation this problem seems to go away if I remove the v.id('tableName') fields in my query/mutation arg validation. Perhaps their is some validation code checks happening before the schema has been updated that it is checking against?

20 replies

CCConvex Community

•Created by ian on 4/18/2023 in #general

Migrating to 0.13.0

I'm getting the following error after upgrading and running convex dev

Error: Unable to push deployment config to https://-------------.convex.cloud
✖ Waiting for all table indexes to be backfilled...
400 Bad Request: UnableToPush: Hit an error while pushing:
InvalidTableNameReference; Your validator contains a reference to `v.id("notebooks")`, but `notebooks` isn't defined in your schema.

Error: Unable to push deployment config to https://-------------.convex.cloud
✖ Waiting for all table indexes to be backfilled...
400 Bad Request: UnableToPush: Hit an error while pushing:
InvalidTableNameReference; Your validator contains a reference to `v.id("notebooks")`, but `notebooks` isn't defined in your schema.

I also added argument validation so I assume there is something related to that but my schema clearly shows that I have notebooks in it:

export default defineSchema({
  users: defineTable(user).index('by_token', ['tokenIdentifier']),
  notebooks: defineTable(notebook),
})

export default defineSchema({
  users: defineTable(user).index('by_token', ['tokenIdentifier']),
  notebooks: defineTable(notebook),
})

Anything I can do to debug this further?

20 replies

CCConvex Community

•Created by ian on 4/18/2023 in #general

Migrating to 0.13.0

Oh, that's great. I had incorrectly assumed I had to wrap my table definitions in v.object() but given that's not the case (and even if it was I realize now I could just use the vanilla object version to create my modified schemas than wrap them in v.object() at the end) it looks like I have everything I need. Thanks for the great examples! 🤦‍♂️

20 replies

CCConvex Community

•Created by ian on 4/18/2023 in #general

Migrating to 0.13.0

Do you know if there are plans to add things like .pick .omit .extend .partial to the schema/values lib (similar to zod.dev)? My specific use case it that I have a mutation that only allows updates to certain fields in a document and it would be great to be able to create a validator with .omit and the document object definition instead of manually specifying (duplicating) the types/validators for the fields I want to be allowed. Make sense?

20 replies

CCConvex Community

•Created by ian on 4/18/2023 in #general

Migrating to 0.13.0

Ah, good call. No real need for the code to be aware of the types if that's the case.

20 replies

CCConvex Community

•Created by ian on 4/18/2023 in #general

Migrating to 0.13.0

Perfect, thanks! Yeah I think v.paginationOpts() would be great. If things like that don't make sense to clutter v then I could see it exported elsewhere.

20 replies

CCConvex Community

•Created by ian on 4/18/2023 in #general

Migrating to 0.13.0

Hi @ian I just posted in #general as well, but I was wondering about types for paginationOpts when using argument validation. Is there a built-in validator for that?

20 replies