Konstantin Nesterov

@bvaughn is it possible to work around this issue by adding virtual InfiniteScroll, which would measure cells before "loading" them?

@bvaughn never mind, I don't think I had a right idea. However I stumbled upon [chrome scroll anchoring](https://blog.chromium.org/2017/04/scroll-anchoring-for-web-developers.html) but couldn't make it work with RV. Am I missing something or...

We recently migrated from prisma to mikro-orm and I would say that this it one of the features that we miss the most. > You can already query for to-many...

We also experienced it

Actually I was the one who contributed it =) I think sometimes people prefer to run TypeScript -> ES7 -> Babel , so perhaps it makes more sense in this...

So I was thinking of something more generic, not only GraphQL-specific

Можете уточнить версию Windows?

+1

What would be the proper way to query data with mikro-orm in GraphQL then? For us the current logic is that `em` is forked for every request via `RequestContext.create` and...

I guess we could fork `em` for every field but then we will be constantly overfetching from the db...