Roy Peled

Temporary solution is to manually provide the location strategy to the app. In your root module add the following: ``` import { LocationStrategy, HashLocationStrategy } from '@angular/common'; @NgModule({ ..., providers:...

Hey @kamilmysliwiec, I've made some improvements that drastically reduce the memory footprint of a GQL server. Could you please verify and merge this?

1) getObjectOrInterfaceTypeNameIfExists - This function was not fixed on the move to map based metadata storage. Now instead of looking inside an entire metadata array, it fetches the item from...

I'd love to have this feature as well.

This request to @futagoza for community help has beed raised may times, but we got no response on that matter. We can only assume this project as abandoned, and together...

Hey @L-Luciano did this merge https://github.com/nestjs/graphql/pull/2666 fixed your issue? try to upgrade nest/graphql to version 11

Hey everyone, sorry for the late reply, I realize it was my refactor of metadata storage that caused this issue. I didn't notice this issue before, and I just got...

For your first point, I think you can accomplish that with spies, instead of creating a new API: ``` const objInstance = {} as unknown as MyClass; const spiedInstance =...

For you second point, not sure that this is the correct behavior (you need to specify exactly what output you want to get from mocks with when clauses), and it...

I agree, we should try to add jsdoc annotations to the code, which most IDEs support. This will be a ongoing effort