Support `--success` with `npx convex dev --tail-logs`
Maybe
--tail-logs-success as an additional flag? (or by default)11 Replies
Running the logs command concurrently doesn't seem to produce the compounded noise that I thought it would for errors, so maybe that's the best way to do this.
Bump on this - I'm noticing the other tools running in dev, like next, are logging every request. I think devs are used to this, would be nice for convex dev to do the same by default.
I don't understand the request here, do these just not work together?
No, they do - I guess my follow up here is changing the original idea a bit. Building boilerplates, I'm noticing that when I run convex dev alongside other commands, I expect it to just log things, even though I've used it for a long time. So I suspect other devs will, too. Starting up a new project and feeling like convex isn't doing anything because it isn't logging anything feels like a drawback.
Especially when your frontend dev server is logging every request.
So I'm suggesting we consider --tail-logs + --success behavior as the default for convex dev.
What does --success mean here, that non-errors are also logged?
Right, the equivalent of
convex logs --successHelpful to hear! probably a slower process to make it the default but we can add a --tail-logs-including-success or something and add it to templates
yeah that would bridge the gap at least
great point that "knowing if something is working" is huge
could certainly get noisy if it's every useQuery rerun in an active site but maybe that's fine
Like, I've had frustrations with this, where I'm troubleshooting an issue for a bit, and then realize I didn't have logging going in a separate cli, and that convex is actually working
so then I either go open the dashboard and check logs, or open a separate cli to get logs
an issue is this is also where compile errors go
but that's how e.g. Next.js does it, so maybe fine
yeah for my own ongoing dev work, I use success logging and have never been annoyed with it (just as a data point)
next also has errors block your UI, which we don't have, so maybe burying errors would be a problem at scale