Greg Peden

I'm considering contributing a PR for this. I am just studying the code base to see if I think I am up to tackling this.

Yeah @SuperDJ's example is simpler to understand than mine. In my case I was wanting to run a aggregation as a subquery to avoid N+1 problem. Since then you have...

I beat you to it... had a kid 7 weeks ago. ;) But I am currently using laravel-websockets myself. After I meet internal company deliverable goals (on which I am...

For what it's worth, I wouldn't get too lost in the weeds if that leads to no progress on this. Most often identical queries are going to be coming from...

BTW I just changed my username from SirLamer to @gregpeden, sick of the user name from when I was 10 years old. ;)

Your point on presuming it to be private is apt, or perhaps allow a global setting which defaults to private. I don't think "public" is the correct label, for example...

Just reporting that I am finding the same thing happens with my custom "JSON" scalar - it is saved in the job queue in its parsed state (as an array)...

See the issue I cross-referenced to here for some additional discussion. TLDR: The variables end up looped through "executeQuery" twice, once on the first submission, and again when the Subscriber...

Remember that if you turn off parsing on the second run then some items may fail to substantiate for the broadcast event because the subscriber data is recalled from memory...

I have tried my best to find a clean solution but I think it's gonna take a more systematic solution than what I can affect without changing lots of other...