Making this lib comparable to HotChocolate in terms of features

[kasir-barati]

Hey folks,

I wanted to see if there is any plan for how to develop and add new features to this lib. To be perfectly honest with you I was at first disappointed that we do not have something as capable as HotChocolate. But then I found this lib and I am really happy about it since now we can find our way towards a feature-rich GraphQL server with ease by leveraging this library.

I know it feels like a long shot but I think it is possible. On another note I am planning to use this lib extensively in my personal or work related projects. So I am already on-board, the only thing that I lack at the moment are:

• A bit of insight into this lib intricacies (Any comment or pointer would be much appreciated 🙂). But I am also working on it.
• I migrated from RESTful API landscape to GraphQL. So I am relatively new to this setup and still needs to learn a lot. But I have been using GraphQL already a lot lately and going forward my exposure to it is just going to increase.

Any comment?

[TriPSs]

Always open on PRs/feedback/ideas to improve this lib, so everything is welcome!

[kasir-barati]

Some housekeeping todos that IMO are broken windows

• Very long lines of code which makes it kinda hard to understand.
• moduleResolution should be changed to NodeNext.
• Change the hard to understand names like DM, DOSA which frankly I can kinda figure them out but nonetheless it is not very intuitive. You need to pause and poke around to understand them.

Kinda Falls Under the Category of Nitpicky

• jest.e2e.js can go inside the examples dir.
• Update the compose file syntax (remove version from it, rename it to compose.yaml).
• Maybe pnpm instead of yarn for the sake of faster installation and needing less space on our local machines.

PRs

1. chore: typed jest conf + remove version from compose file + fix typo #337