Using TypeScript for Frontend and Python for Backend
Hey everyone! I have a question about this section that says "Improved Typescript Skill" . I'm wondering if it's okay to use TypeScript exclusively for the frontend while using Python for the backend. Do I need to build the entire stack with TypeScript, or can I focus on TypeScript for the frontend and Python for the backend separately?
Roles / Permission modeling (Ent Tables)
Hi, I'm pretty new with backend paradigm but i'm a seasoned frontend dev. Convex enables me to do stuff that would take me a lot of time learning with traditional backend programming - i'm am grateful for it.
So my question is, is there a better way to do this Role / Permission using Ent
edges instead of foreign keys? What's the common best practice and pattern I should know....
Error: Unexpected type of undefined
In my
nextjs app, I'm using preloadQuery to load and render a query inside a Server Component:
```typescript
...
// this is a server component
const localesQuery = preloadQuery(api.locales.get.default, {...
[Module: server/TS]: Generic query pipelining
Hello, I am trying to build a custom react hook that contains a "pipeline" of Convex functions. The pipeline is simple: Query A returns an array of Id<Table>, and Query B accepts an array of Id<Table> and enriches them (basically performing joins with other tables):
() => getDocumentIds --> (Ids) => enrichDocuments(Ids)
I want to make this hook generic such that it can be used with any compatible getter/enrichment function pair, e.g. both getVideoIds --> enrichVideos and getChannelIds --> enrichChannels. Therefore, the return type of Query A must be compatible with the parameter type of Query B. I have taken inspiration from the implementation of useQuery and have actually made it work in practice, but not without ignoring a TS error - not very peace of mind-y.
I found that specifying Args in the FunctionReference of QueryB approximated the solution, but I had to manually specify the correct object key (e.g. "videoIds"). Is there a way to use some placeholder as such?: { PLACEHOLDER: FunctionReturnType<BaseQuery> }...