Timofei Iatsenko

Ok, i will take care of that

@dzunftmeister-evorhei Hi, i was able to reproduce your issue. The root cause is not related to `introspectComments` but related to GraphQL plugin itself. @kamilmysliwiec the root cause is in the...

Well, now i know more insights about this graphql plugin and understand why we need this "eager" imports. This issue quite hard to tackle, but i have an idea how...

Pushed a workaround into PR, waiting for maintainers...

My changes is not a fix but rather a workaround. It allows developer to override default behavior and completely switch off type introspection for one particulare field. With my changes...

I also worked on the type-checker free version in another branch, but decided to delay it for a while, because there are so many cases to tackle and impact on...

@koriwi By the way, could you prepare a mimimal repro copying your monorepo structure, i will look, may be we can fix it differently.

When you rename your file and deleted suffix `.entity.ts` you just excluded this file from typescript plugin transformation. The effect is the same as just disable this plugin at all,...

I add a bit of my thoughts. Actually, you don't need to have your calculated fields (`@ResolveField()` in resolver) in your model. The framework will merge declarations from your entity...

> This problem is a common issue for javascript projects, not only effector based. I totally not agree with this sentence. I've never had such problems in pure React projects...