Abdul Posts - Convex Community

Abdul

•Created by Abdul on 3/10/2025 in #support-community

Mapping telegram user ids to Convex users

is there a way to just tell Convex "this user is authenticated" and then call the actions and have ctx.auth.getUserIdentity() return the user? I have a use case for telegram bot where I am looking up user by their telegram user id and then calling the actions that depend on ctx.auth.getUserIdentity(). I want to avoid the need to pass telegram user id to the convex actions and want to have the same experience for telegram users as a user calling via convex react client. I am using Clerk as auth provider and have users synced users between users table and Clerk. users tables has telegramUserId field which I am using for looking up user when handling webhook requests

8 replies

CCConvex Community

•Created by Abdul on 1/6/2025 in #support-community

Type instantiation is excessively deep and possibly infinite.

I’m encountering the following TypeScript error in my project: Type instantiation is excessively deep and possibly infinite I’m new to TypeScript and don’t have much experience with its type system. My project has a complex directory structure with multiple levels of nesting, and I suspect the deeply nested structure might be causing the issue. Here is how directory structure roughly looks like:

project-root
├── generated
│   ├── api.d.ts
│   ├── api.js
│   ├── dataModel.d.ts
│   ├── server.d.ts
│   └── server.js
├── core
│   ├── index.ts
│   ├── utilities.ts
│   └── types.ts
├── modules
│   ├── featureA
│   │   ├── helpers.ts
│   │   ├── logic.ts
│   │   ├── types.ts
│   │   └── subFeature
│   │       ├── core.ts
│   │       ├── subLogic.ts
│   │       └── subTypes.ts
│   ├── featureB
│   │   ├── handlers.ts
│   │   ├── queries.ts
│   │   └── types.ts
│   └── shared
│       ├── auth.ts
│       ├── config.ts
│       └── utils.ts
├── queries
│   ├── featureAQueries.ts
│   ├── featureBQueries.ts
│   └── sharedQueries.ts
├── schema
│   ├── entities
│   │   ├── entityA.ts
│   │   ├── entityB.ts
│   │   └── entityC.ts
│   ├── relations.ts
│   └── types.ts
└── webhooks
    └── eventHandlers.ts

project-root
├── generated
│   ├── api.d.ts
│   ├── api.js
│   ├── dataModel.d.ts
│   ├── server.d.ts
│   └── server.js
├── core
│   ├── index.ts
│   ├── utilities.ts
│   └── types.ts
├── modules
│   ├── featureA
│   │   ├── helpers.ts
│   │   ├── logic.ts
│   │   ├── types.ts
│   │   └── subFeature
│   │       ├── core.ts
│   │       ├── subLogic.ts
│   │       └── subTypes.ts
│   ├── featureB
│   │   ├── handlers.ts
│   │   ├── queries.ts
│   │   └── types.ts
│   └── shared
│       ├── auth.ts
│       ├── config.ts
│       └── utils.ts
├── queries
│   ├── featureAQueries.ts
│   ├── featureBQueries.ts
│   └── sharedQueries.ts
├── schema
│   ├── entities
│   │   ├── entityA.ts
│   │   ├── entityB.ts
│   │   └── entityC.ts
│   ├── relations.ts
│   └── types.ts
└── webhooks
    └── eventHandlers.ts

Are there general best practices for handling query and mutation definitions in a project with this kind of nested structure?

3 replies

CCConvex Community

•Created by Abdul on 12/30/2024 in #support-community

Unable to push deployment config when using @react-pdf/renderer

15 replies