Tim
I don't think it will work for every client though. Which one are you using?
@mikearnaldi This was an idea for a more flexible annotation system for Cause. Maybe something for 4.0?
> We used to have annotations but we removed them in favor of carrying the span in a proxy due to re-fail losing the span This goes the route of...
> Will need to check the details but as far as I understand it's not really possible, spans are linked to a specific error, re-failing with a different error should...
You will need to embed the finalizers into the stream itself, as bun consumes the stream after the response headers are sent.
You can also use .unwrapScoped https://effect.website/play#5c892bc6d169
We made `YieldableError` extend `Inspectable` which adds those methods. I have found a way to get `cause` to render, while preserving the custom `.toString` behaviour. We can't remove those methods...
I think this should just live in platform-browser, I can't see us adding implementations for any other platform.
When I get some time I'll do another review
Did a bit more work on this to try clean things up. Still needs work: - support for schema classes with auto-incrementing keys, maybe add `IndexedDb.AutoIncrement` schema - insert /...