Route Translation for SDK Autogeneration (kebab-case filenames to camelCase API)
Context:
I'm using Convex on several small freelance projects and exploring its integration into larger projects within a corporate environment. The established TypeScript filename convention in this environment is kebab-case (e.g., my-functions.ts).
Currently, the SDK autogeneration process creates API routes directly from these filenames, resulting in function access like api["my-functions"].functionFoo.
Desired Behavior:
I would love a "route translation step" during SDK autogeneration. This would allow mapping kebab-case filenames to camelCase API routes. For example, a file named my-functions.ts containing functionFoo would be accessible via api.myFunctions.functionFoo.
This feature would significantly improve the developer experience, particularly in environments with existing coding standards.
If needed, I'm open with potentially contributing to this feature. While I'm relatively new to Convex, I have experience with both TypeScript and Rust (though I believe this change would primarily involve TypeScript). I'm open to exploring the codebase and assisting where possible as I gain more familiarity with Convex on a larger project.
1 Reply
Thanks for posting in <#1088161997662724167>.
Reminder: If you have a Convex Pro account, use the Convex Dashboard to file support tickets.
- Provide context: What are you trying to achieve, what is the end-user interaction, what are you seeing? (full error message, command output, etc.)
- Use search.convex.dev to search Docs, Stack, and Discord all at once.
- Additionally, you can post your questions in the Convex Community's <#1228095053885476985> channel to receive a response from AI.
- Avoid tagging staff unless specifically instructed.
Thank you!