Prince
Prince
CCConvex Community
Created by Dhruv Kumar Jha on 5/29/2024 in #support-community
Can we customize the convex public/deployment url?
Lovely, thanks mate appreciate the update
12 replies
CCConvex Community
Created by Dhruv Kumar Jha on 5/29/2024 in #support-community
Can we customize the convex public/deployment url?
Hey @james - any updates on this?
12 replies
CCConvex Community
Created by Prince on 6/1/2024 in #support-community
Dashboard crashing, webhooks not receiving requests, and logs not showing on new project
resolved, temporary issue affecting new deployments. Thanks Convex team.
5 replies
CCConvex Community
Created by Prince on 6/1/2024 in #support-community
Dashboard crashing, webhooks not receiving requests, and logs not showing on new project
thanks for taking a look
5 replies
CCConvex Community
Created by Prince on 5/22/2024 in #support-community
.paginate() result type returning a single document, not an array of documents
skimmed the docs but it is very clearly explained there
7 replies
CCConvex Community
Created by Prince on 5/22/2024 in #support-community
.paginate() result type returning a single document, not an array of documents
thank you
7 replies
CCConvex Community
Created by Prince on 5/22/2024 in #support-community
.paginate() result type returning a single document, not an array of documents
ah, I am an idiot
7 replies
CCConvex Community
Created by Prince on 5/22/2024 in #support-community
.paginate() result type returning a single document, not an array of documents
No description
7 replies
CCConvex Community
Created by Prince on 5/22/2024 in #support-community
Query type definition does not include all possible return scenarios
great idea
44 replies
CCConvex Community
Created by Prince on 5/22/2024 in #support-community
Query type definition does not include all possible return scenarios
this is great though thanks Michal
44 replies
CCConvex Community
Created by Prince on 5/22/2024 in #support-community
Query type definition does not include all possible return scenarios
would be ideal if it recognised without it being forced into it
44 replies
CCConvex Community
Created by Prince on 5/22/2024 in #support-community
Query type definition does not include all possible return scenarios
No description
44 replies
CCConvex Community
Created by Prince on 5/22/2024 in #support-community
Query type definition does not include all possible return scenarios
pain
44 replies
CCConvex Community
Created by Prince on 5/22/2024 in #support-community
Query type definition does not include all possible return scenarios
No description
44 replies
CCConvex Community
Created by Prince on 5/22/2024 in #support-community
Query type definition does not include all possible return scenarios
must just be an issue on my end if you cant reproduce
44 replies
CCConvex Community
Created by Prince on 5/22/2024 in #support-community
Query type definition does not include all possible return scenarios
No description
44 replies
CCConvex Community
Created by Prince on 5/22/2024 in #support-community
Query type definition does not include all possible return scenarios
I just broke apart some of the ternary steps to check type defs but sure
44 replies
CCConvex Community
Created by Prince on 5/22/2024 in #support-community
Query type definition does not include all possible return scenarios
export default defineSchema({
users: defineTable({
// this is UserJSON from @clerk/backend
clerkUser: v.any(),
admin: v.optional(v.boolean()),
}).index("by_clerk_id", ["clerkUser.id"]),
reports: defineTable({
vapiId: v.optional(v.string()),
userId: v.optional(v.id("users")),
transcript: v.optional(v.any()),
status: v.optional(
v.union(
v.literal("waiting"),
v.literal("processing"),
v.literal("ready"),
v.literal("failed")
)
),
title: v.optional(v.string()),
summary: v.optional(v.array(v.string())),
diagnosis: v.optional(
v.array(
v.object({
name: v.string(),
differentials: v.array(v.string()),
demographics: v.array(v.string()),
symptoms: v.array(v.string()),
indicators: v.array(v.string()),
contraindicators: v.optional(v.array(v.string())),
prognosis: v.string(),
treatment: v.string(),
tests: v.array(v.string()),
})
)
),
referrals: v.optional(
v.object({
referrals: v.array(
v.object({
specialist: v.string(),
recommendation: v.string(),
})
),
tests: v.array(
v.object({
item: v.string(),
description: v.string(),
})
),
})
),
recordingUrl: v.optional(v.string()),
cost: v.optional(v.number()),
duration: v.optional(v.number()),
})
.index("by_user", ["userId"])
.index("by_vapi_id", ["vapiId"]),
})
export default defineSchema({
users: defineTable({
// this is UserJSON from @clerk/backend
clerkUser: v.any(),
admin: v.optional(v.boolean()),
}).index("by_clerk_id", ["clerkUser.id"]),
reports: defineTable({
vapiId: v.optional(v.string()),
userId: v.optional(v.id("users")),
transcript: v.optional(v.any()),
status: v.optional(
v.union(
v.literal("waiting"),
v.literal("processing"),
v.literal("ready"),
v.literal("failed")
)
),
title: v.optional(v.string()),
summary: v.optional(v.array(v.string())),
diagnosis: v.optional(
v.array(
v.object({
name: v.string(),
differentials: v.array(v.string()),
demographics: v.array(v.string()),
symptoms: v.array(v.string()),
indicators: v.array(v.string()),
contraindicators: v.optional(v.array(v.string())),
prognosis: v.string(),
treatment: v.string(),
tests: v.array(v.string()),
})
)
),
referrals: v.optional(
v.object({
referrals: v.array(
v.object({
specialist: v.string(),
recommendation: v.string(),
})
),
tests: v.array(
v.object({
item: v.string(),
description: v.string(),
})
),
})
),
recordingUrl: v.optional(v.string()),
cost: v.optional(v.number()),
duration: v.optional(v.number()),
})
.index("by_user", ["userId"])
.index("by_vapi_id", ["vapiId"]),
})
44 replies
CCConvex Community
Created by Prince on 5/22/2024 in #support-community
Query type definition does not include all possible return scenarios
No description
44 replies
CCConvex Community
Created by Prince on 5/22/2024 in #support-community
Query type definition does not include all possible return scenarios
5.4.5 yep
44 replies