Title of function with export name
In the admin dashboard, it would be ideal if the function names matched the type generated naming of
{fileName}:{exportName}. It appears if there is an export name, its just using that for display purposes.
I am using a naming convention of internal to denote internal functions, and these are indistinguishable from the dashboard.
9 Replies
oof! That's not ideal!
Thx for pointing it out.
One other minor note with this UI.
When running functions it only outputs error level logs. This requires me to toggle between the log stream tab and back to get other relevant levels to debug the issue.
It would be nice if it shared all log output for the execution, especially if it errs.
cc @ari
Hey Allen! I've queued up work to to distinguish the actions that share names and will ping ya once that's deployed (this week)
Thanks for the feedback on the function runner -- your vote helps us move this work up the priority list 🫡
Here are a couple features I'd love to add -- if you had to pick only one, which would it be?
1. Have the function runner be global on the dashboard, allowing you to navigate around with a “companion” function runner
2. Integrate log output into the existing function runner, so you see logs inline with the return value
I would say without #2, #1 isnt compelling. I would focus on making the function runner more feature complete before making it more accessible.
The greatest drawback in developing convex apps is the lack of true debugging. I cant setup breakpoints in my backend code and inspect runtime state. Anything that gets me closer to this in the function runner is a huge step forward to parity with other frameworks that allow local execution and proper debugging.
Thanks, that's helpful info for us to calibrate on. We've taken note on integrating the logs into that view, as well as the feature request to add breakpoint debugging.
A hint for now would be to check out your browser console -- the logs from your functions will be there (albeit all at the INFO level).
>check out your browser console
Are you referring to when invoked from the app or invoked from the function runner?
You should see it in both locations, but in this case I was referring to the function runner 😃
Not intended to be a long term solution! I'd like to capture that output and have it be available directly in the UI
@allen deploy distinguishing function names exported from files with one named export is out -- they now appear as
file_name:function_name in the file tree. Thanks again!thanks!