Gabriel Grubba

Could not figure out why tests on the server fall on standard error while ones for clients fall on the new ones any ideas @zodern ?

Made the tests work properly. On the client, it throws the correct error messages that were the focus of this PR would you like to add something @zodern?

Hello there! have tested it, and this issue actually happens. Also, I've thought of a workaround for your problem: ```jsx {Array.isArray(task.hash) && task?.hash?.map((item, index) => { const key = Object.keys(item).at(0);...

Now I think I got everything. the only thing that I'm thoughtful is the order of the validations: ```js if(!(id.startsWith('.') || id.startsWith('/'))) { throw err; } if (id.endsWith('client') || id.endsWith('server'))...

I've done this adjustment! and added some tests for the case that I've mentioned

Sure! @lapaz17 is free to be taken, if you need any help solving this issue you can reach out here on this issue or you can create a draft Pull...

Hey @lapaz17, I think it would work if given a reproduction of a test scenario for this. I would add tests in ``packages/ddp-client/test/livedata_connection_tests.js``

It was merged and will be correted in the next release :tada:

Hey, @zodern is there any status on this? probably will be closing this and some others by end of the month

I believe there is no problem in removing this section. As you said in the PR description, it is an unmaintained package. The only possible downside is the lack of...