Alexandr Marchenko

Maybe `NO_COLOR` deserves a separate issue It should be much easier to implement and may not wait for color styles

Accidentally did push packages upgrade, everything still working (tests and example server) While upgrading added missed `concurentlly` package If you want I can try to revert it and make separate...

Got it, to reproduce you gonna need update graphql-tools package to latest v5, then you gonna need to change your `transform-federation.spec.ts` by removing mocks and adding code from example then...

Hm, seems like I did get into version mismatch between projects and it seems that we will have similar issues for a while until graphql v15 and graphql-tools v5 becomes...

BTW most of [documented](https://www.apollographql.com/docs/graphql-tools/schema-transforms/) transformations are available only in graphql-tools@5, so for example at moment we can not remove fields on type with `FilterObjectFields` because it is introduced in graphql-tools@5

Yes and no, oh it was so long time ago, I even do not remember all the details Instead of having separate mesh/transformer/whatever service I just bring code pieces directly...

Some kind of `Order` annotation may lead to even more confusion, e.g.: ```csharp class User { [Order(1)] string Id string Foo [Order(1)] string Name string Bar int Acme } ```...

Indeed, we are observing something similar issue but in microservices setup mode, which allows us to identify that distributor eats memory and being OOM killed Many thanks to @joe-elliott for...

At moment playing with ko.editables, and do not have such troubles, while using separate view models here is a [demo](https://jsfiddle.net/mac2000/02f7weum/embedded/result,js,html/) so may be that is not a problem at all...

look at [action.yml](https://github.com/trufflesecurity/trufflehog/blob/main/action.yml#L33) the action itself just runs docker image and passes whatever you want via extra args, with that in place you may achieve that like so: ```yaml -...