Fredrik Enestad

As of encore v1.48.0 we no longer run `mustBeSet` for the set-cookie header in a browser context. But we've also added support for adding cookies in your api schemas, see...

You can use unions, just not on the root level, so you could do something like: ```ts export type LoginSuccess = { ok: true; param1: string; }; export type LoginFailure...

@CodeWithOz Could you try upgrading to latest encore version and see if that resolves the issue? we recently have made some improvements to the type resolve that would cause this...

I think https://github.com/encoredev/encore/pull/1631 should solve both the problems. Redirects will be possible through custom status code and setting headers

The middleware pr have been released now (version 1.45.3), you can update encore by running `encore version update`

I've been trying to reproduce this, but without any success. Do you also have lots of node.exe processes left @CRBroughton ? Could you in a separate terminal run `encore daemon...