Attila Večerek

@Urigo I've just removed the no longer necessary patch of `@urql/[email protected]`. The fix was added in `v0.3.3`. I think it should be ready for another attempt at running the CI....

It's a mystery to me why I'm getting the following error during the build step: ``` Type 'import("/Users/avecerek/Code/graphql-code-generator-community/node_modules/@graphql-codegen/visitor-plugin-common/typings/utils").DeclarationBlock' is not assignable to type 'import("/Users/avecerek/Code/graphql-code-generator-community/packages/plugins/c-sharp/c-sharp/node_modules/@graphql-codegen/visitor-plugin-common/typings/utils").DeclarationBlock'. ``` This PR does not touch...

The problem is introduced in https://github.com/dotansimha/graphql-code-generator-community/pull/701/commits/873debdf76aa905ebfd8412c10122b03ea573678. I have no clue why but yarn suddenly resolves the `node_modules` differently after a new package is added. I'm lost. Could someone more knowledgeable...

My strategy to take this work further is to modernize the tooling first. I'd appreciate it if one of the maintainers could take a look at #735 🙇

@tim-smart ~I think my [original PR](https://github.com/tim-smart/sqlfx/pull/87/commits/c40f53108ce94b8c11d9c4f9a2d565382f9b29c5) adding support for binary values isn't quite up to the challenge 😄~ NVM: ```ts import { Array } from "effect" const u = new...

This is probably an issue in [mysql2](https://github.com/sidorares/node-mysql2/issues/2528) itself. I'll try to replicate it using mysql2 directly.

This is very annoying, especially on large monorepos and it's happening on yarn v3.2.0 as well 🙁