[Enhancement idea] Move the Mongo and Knex query builders upstream into their own project

[craicoverflow]

Describe the solution you'd like

The Knex query mapper and Mongo query mapper implementations are really useful to Graphback but they could also be valuable as upstream projects (outside of the Graphback monorepo) so they can be easily imported into other Node.js projects looking to use GraphQLCRUD in their projects.

Since these are fairly hidden nobody will know about them unless they are using Graphback, then they could import them separately to access this feature but it means importing @graphback/core and lots of extra stuff they probably don't need.

• @graphback/runtime-mongodb#buildQuery
• @graphback/runtime-knex#createKnexQueryMapper

This is the lowest of the low priority, but it could be a great enabler for GraphQLCRUD adoption in the future.

[machi1990]

Automatically generated comment to notify maintainers
/cc @machi1990, @wtrocki

[namit-chandwani]

Hey, I'm interested in working on this issue.
Can you please let me know what would be a good starting point for this?

[craicoverflow]

Hi @namit-chandwani you can ignore this one - it is something maintainers would need to do because you would have to create repos in the aerogear org etc.