Philipp Steinrötter
Philipp Steinrötter
Yes, enabling fieldResolverEnhancers has performance impacts and would require all other enhancers to check whether it is a field or not as shown in the NestJS documentation. I guess we...
I am a bit under water right now - I will try to get to it by the end of next week!
@doug-martin I have been doing some small PoCs and right now I am thinking that one global authoriser might be the best "it just works" solution. Since I am out...
@doug-martin @lukasender I am working on finalising the global auth PR and have come up with a few points I would like to get your input on. With the new...
+1 I would also like to happen if its enough to patch the repositories and having one transactional decorator to have any methods using the repository after the decorator to...
I was able to mock it using ``` jest.mock('typeorm-transactional-cls-hooked', () => ({ Transactional: () => jest.fn(), })); ```
@doug-martin I continue to have problems after committing an updated package lock. Could you have a look into it?
I guess its safe to say that not all dbs that TypeORM or sequelize support are able to work with array columns. When using TypeORM, you can use the [simple-array...
I think just executing many requests from the frontend should be a fairly reasonable solution. See a discussion on batch queries here: https://github.com/FormidableLabs/urql/issues/800
Since this is specific to TypeORM, I wouldn't suggest adding it into nestjs-query. However, it should be fairly simple to publish events to the same pubsub topics that are used...