Sergio Moreno
Sergio Moreno
Any suggerence mate? I'm migrating some repos that are not too much complicated to the new types to check if there's any extra issue @tianzhich
@haikyuu i hope this is not a problem to you =)
Well @haikyuu thanks for letting us rape your project a bit haha It's all the types fixed, if you find any issue feel free to notify us!
It's curious because sometimes it works and sometimes not; Edit: just checked that works fine if I change some component of the UI but not If I change only the...
In our case after adding `jsonProtocol` to the schema, our testing suite it's failing because `in` it's expected to be always an string[], but without `jsonProtocol` and also the types...
Latest dev (4.14.0.dev.9) package works like a charm on our side, more than 2000 tests passed correctly without touching anything, on our side we weren't running on any performance bottleneck,...
Same here, any guidelines? Edit; on my side it has been fixed using SHA1 instead of sha512
How far @thekip are we of converting this feature in something stable? Probably if you detail which tasks are pending I can help on my free time :) We noticed...
I know that Vitest instead of using jest-worker is using Piscina https://www.npmjs.com/package/piscina which is more robust by far than jest-worker, probably could be a good addition here
 I'm still getting this issue, returning twice when is triggered the subscription