Nipunn Koorapati

this should be out!

Yep interesting finds! Sounds like you have a good workaround here, but a more fundamental improvement would be to maintain object references if query results don't change. @thomasballinger might have...

do you possibly have more than one docker image running? That error arises if the admin key is from one deployment but being used on another one. I doubt docker...

The pattern that the CLI is designed for - is to put the modules under the `convex/` directory. If everything is in the configured convex/ directory, then `convex dev` will...

From reading the source, my understanding is that the desired behavior is actually that any files that are read in the bundling phase become part of the `observedDirectory` set and...

If it's fully flagged off as a user option, seems reasonable. It will be worth measuring the difference in size of the fully built docker container - to understand the...

yep seems like a styling bug. Probably won't get around to it soon, but good to know. A nice high quality PR that solves the issue and includes some before/after...

Hi! Thanks for the message. From here, you can see that `null` is a valid convex value, while `undefined` is not. https://docs.convex.dev/database/types Serializing `undefined` isn't so simple, as we've chosen...

I think that sort of helper seems like a good way to go if you want the ergonomics for patching and care a bit less about null values. If you...

Yep that's right. Honestly - from design perspective, `db.patch` is a bit confusing. It only patches at the top level (not nested fields) and the behavior around `undefined` being the...