André Eriksson

Thanks @rewop. We don't have a good way of distinguishing between client generation for frontend use and for backend use at the moment, but until we do it's a better...

The desired behavior isn't really about comparing environments. It should accept a list of environment types and report whether any secret doesn't have a value for any of the provided...

No, secrets can be configured for four different environment types (local, PR envs, dev, and prod). See https://encore.dev/docs/primitives/secrets

Thanks @melkstam, this is a bug and not intended. Will fix.

Hey @ElliottDenlinger, great question! For this issue, since it requires some design work (designing what the API should look like, before coding up the implementation) it's probably easiest to first...

Sure, thanks @ronaudinho!

The `errs` package is primarily for API errors, and while the `sqldb` errors currently return `*errs.Error` objects I think that was a design mistake. My gut feeling is that we...

Thanks @Minivera for writing this up! Totally agree with the direction and the API sketch mirrors my thinking. The main thing we need to figure out is the API surface...

Thanks @theGlenn for the detailed report! Will try to reproduce.

What's the use case for having "two services have the same subscription name"? A subscription can only be tied to a single service.