The `function-spec` command is broken
If you have a literal bigint in in your function schema, it crashes.
https://github.com/get-convex/convex-backend/issues/212
Additionally, the generated schema reports "JavaScript numbers" aka. doubles/floats as integers.
https://github.com/get-convex/convex-backend/issues/213
I opened Github issues for this and am opening here to for more visibility.
PS: Additionally, it seems that the
--file options is broken as well.GitHub
npx convex function-spec crashes on literal BigInt · Issue #212 ...Running npx convex function-spec on an environment which has the following function crashes: export const query12 = query({ args: { i: v.literal(BigInt(1)), }, returns: { i: v.literal(BigInt(1)), }...
GitHub
npx convex function-spec Reports incorrect literal · Issue #213 ...The following task: export const query10 = query({ args: { i: v.literal(1), }, returns: { i: v.literal(1), }, handler: (ctx, args) => { return args; }, }); Will produce the following schema: { &...
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!