alexcole Comments - Convex Community

alexcole

•Created by n8 on 5/5/2023 in #support-community

Websocket closed error

For anyone else following along, we're discussing the same problem at https://discord.com/channels/1019350475847499849/1108758055677599795/1108772913114521740

16 replies

CCConvex Community

•Created by whoami on 5/18/2023 in #support-community

Bad URL errors "WebSocket closed unexpectedly with code 1006" in vercel preview env + convex dev

Sorry this has been such a pain to debug. Let's try a few more things to get to the bottom of this: 1. Can you DM me preview link? I'd like to see if this happens for me too. 2. This happens in multiple browsers (Chrome and Firefox), correct? 3. What kind of network are you on? Is this home wifi? Is there a firewall? 4. Does this happen on different devices on the same network? Does it persist on a different network (ex your phone on data)? 5. What does this WebSocket connectivity test page show? https://connectivity-test.asana.com/ At my previous company (Asana) we had some major issues with a small number users who had networks that blocked WebSockets. We made that test page to help debug problems.

16 replies

CCConvex Community

•Created by allen on 5/16/2023 in #support-community

Optimistic update from action?

Got it. And is this a single mutation thats fired after the action or could it be one of many mutations? Not knowing your React components, maybe there is still a way to set some state like savingAccessToken: true when the action is fired and rolled back when it completes? Then components know this is happening and render appropriate UI? Definitely hacky. One other idea from @Indy is that you could persist this state to Convex. In this model, your users table could have a property like savingAccessToken: v.boolean(). Then the client could: 1. Fire a saveAccessToken mutation and use an optimistic update to set savingAccessToken: true 2. On the server, the mutation will set savingAccessToken and schedule an action 3. The action will get the access token and run a mutation to save it and set savingAccessToken: false In this way, the client can look at user.savingAccessToken and know when we're in this flow. Kinda annoying though that this creates a new state in your database to represent what is really only a client concern.

6 replies

CCConvex Community

•Created by allen on 5/16/2023 in #support-community

Optimistic update from action?

Sorry, calling actions with optimistic updates isn't supported right now. It's definitely a limitation with calling actions from the client. Because actions can run multiple mutations, take a long time, etc it's hard for us to build correct optimistic updates here. Some ideas on workarounds: If possible, could you restructure your code as a mutation that schedules an action for the work that can't be done in the mutation? Then you can apply an optimistic update to the mutation on the client. If thats not an option, can you handle this manually in your React components? I'm imagining that you set some state along with firing the action and roll that state back when the action completes (the promise resolves). Happy to brainstorm more if you want to share more details about your use case. Sorry again, I know this is a pain.

6 replies

CCConvex Community

•Created by whoami on 5/15/2023 in #support-community

Use `v.` schema to validate object types?

Idk if this works for your use case

11 replies

CCConvex Community

•Created by whoami on 5/15/2023 in #support-community

Use `v.` schema to validate object types?

Oh actually, one more idea: if you use the discriminated union pattern, you don't actually need the validator to tell which case of the union you're in. I'm imagining something like:

// In your schema:
const shapeValidator = v.union(
  v.object({
    type: "triangle",
    sideLength: v.number()
  }),
  v.object({
    type: "circule",
    radius: v.number()
  }),
); 

defineSchema({
  shapes: defineTable(shapeValidator)
});

// In your UI

function ShapeComponent({ shape }: { shape: Document<"shapes"> }) 
  if (shape.type == "triangle") {
    // render triangle here
    // TypeScript will narrow the type to `{type: "triangle", sideLength: number}`
  } else if (...)
}

// In your schema:
const shapeValidator = v.union(
  v.object({
    type: "triangle",
    sideLength: v.number()
  }),
  v.object({
    type: "circule",
    radius: v.number()
  }),
); 

defineSchema({
  shapes: defineTable(shapeValidator)
});

// In your UI

function ShapeComponent({ shape }: { shape: Document<"shapes"> }) 
  if (shape.type == "triangle") {
    // render triangle here
    // TypeScript will narrow the type to `{type: "triangle", sideLength: number}`
  } else if (...)
}

11 replies

CCConvex Community

•Created by whoami on 5/15/2023 in #support-community

Use `v.` schema to validate object types?

Yeah, for right now there isn't a good way to share validators between your schema and your UI. The best approach is probably to duplicate between Convex validators and Zod (or skip the Convex schema validation entirely and call your Zod validator just before db.insert and db.replace). But thanks for the feedback! I'll count this as a vote for Zod support and/or the ability to call Convex validators from JS.

11 replies

CCConvex Community

•Created by whoami on 5/15/2023 in #support-community

Use `v.` schema to validate object types?

Did you want to reuse this validator outside of argument validation and schemas? That's not supported right now, but it is something we could add in the future.

11 replies

CCConvex Community

•Created by allen on 5/10/2023 in #support-community

Optimistic Update on Paginated Query

Yep, I'd also be excited to eventually build more powerful optimistic updates in our client! In the meantime, if you want some example code, there is a optimisticallyUpdateValueInPaginatedQuery helper for editing results of paginated queries (https://github.com/get-convex/convex-js/blob/main/src/react/use_paginated_query.ts#L405). Writing a helper to delete a value should be similar (and maybe we should add a helper for this to our npm package).

13 replies

CCConvex Community

•Created by RJ on 4/24/2023 in #support-community