Armon Khosravi

Agree this would be awesome - curious, was this PR mostly an experiment to gauge feasibility?

Hitting this as well - had ran into this issue after attempting [the fix](https://github.com/facebook/react/issues/24437#issuecomment-1127022094) (updating `react-devtools-core` resolutions) for this similar issue: https://github.com/facebook/react/issues/24437

@zhxnlai I have a similar issue in that I have similar but different WebSocket events coming from my backend. A single incorrect or multiple incorrect `@Receive` streams are emitting in...

I might be wrong but from looking at Scarlet and the GsonMessageAdapter, to me it looks possibly like the adapter is relying on an exception being thrown by the generated...

After messing around with Scarlet and the GsonMessageAdapter it appears the issues described in my previous post were what's causing every stream to emit. Currently we are passing each `@Receive`...

I never put it up in a PR since the solution doesn't seem great as we're modifying an annotation based on a specific use case. Furthermore you can implement this...

Sounds similar to https://github.com/Tinder/Scarlet/issues/37