Closed hrvojepavlinovic closed 3 years ago
Not complicated at all, actually, the only part of the package that currently uses dependencies of @nestjs/graphql is the annotation for the argument types. You are right though, it should be able to support all TypeORM + GraphQL projects regardless of framework so I will focus on removing it as a dependency. Feel free to submit a PR as well if you should choose to do so
@wesleyyoung that's great, thanks for quick response 😄
I'll submit PR then 👍🏽
@wesleyyoung here's PR 😄 https://github.com/wesleyyoung/perch-query-builder/pull/2
I thought I wrote a reply but it looks like I forgot to hit save 😨 it looks like this PR actually removes support for NestJS rather than just adding additional support for type-graphql projects. The challenge lies in the @ObjectType annotation. I almost wonder if the object types should be their own packages/plugins so that the Perch repository can remain neutral and merely consume them as specified in the resolver.
@wesleyyoung it seems like it would be simpler to fork it and create 2 separate versions, but meanwhile we made some workarounds so this isnt' necessary anymore. Thanks for assistance though 👍🏽
This package is really great, but I was wondering how complicated would be to add support for projects that don't use NestJS, but only Typescript and GraphQL?
I've checked source code and found out that both @nestjs/graphql and graphql are added as dependencies in package.json.
I'm wondering what would happen if only graphql was used and imported everywhere instead of one from nestjs?
I've never used NestJS, so I'm not aware of possible issues, but I'm sure that it would expand user base by lot if this feature is added.