Add Example Project for Building GraphQL APIs with Pylon using Hono

[schettn]

Hello Hono Maintainers,

I am the creator of a code-first server framework called Pylon for building GraphQL APIs. Pylon simplifies the process by allowing developers to define any TypeScript functions, which Pylon then analyzes to automatically generate a GraphQL API. This approach eliminates the need to write any schema.

I believe it would be beneficial to include an example project in the Hono repository to demonstrate how Pylon leverages Hono and how it can be extended directly with Hono.

This example project would serve as a starter kit for building GraphQL APIs with Hono in an easy and streamlined manner using Pylon. I think this integration could greatly benefit both the Hono and Pylon communities by providing a practical, ready-to-use example.

For more details on how Pylon uses Hono, you can refer to the Pylon documentation and the specific Hono integration section.

If you are interested, I would be happy to prepare and submit a pull request with the example implementation.

Thank you for your consideration.

[simplenotezy]

Interesting project you got going @schettn - agreed it would be nice to get some graphql support into hono. Also just added this issue https://github.com/kimyvgy/worker-apollo-server-template/issues/57

[schettn]

I have created a PR. #140

Feel free to try it out

[yusukebe]

Hi @schettn !

Pylon looks great! I think it's better not to put the example in this repo because we want to have more general examples in the repo. And to keep it simple, we don't have too many projects. So, I suggest adding the example code or description of Pylon to Snippets in the Hono website. There is an "Integration" section, so it will be the best place.

[schettn]

Sounds great. I will prepare a PR there and close #140.

I have also created an issue in the starter repo honojs/starter#40. I think Pylon would fit better there than in examples (alongside Integrations).

One thought on Snippets:

I have never ever checked out the Snippets because I didn't think that it would include the content it includes. For me Snippets are just some quick copy paste examples that I do not need when I understand Hono. I would never imagine that there could be content for Integrations or Ecosystem examples.

I think that renaming "Snippets" to "Integrations" on your website would lead to much more clicks because people are more interested in integrations.

What do you think? @yusukebe

[yusukebe]

I think that renaming "Snippets" to "Integrations" on your website would lead to much more clicks because people are more interested in integrations.

That sounds good! I'm not sure if it would be good to rename it, but it would be great to create the independent "Integrations" section. I'm now working on the documentation matters, so please wait a bit.

[schettn]

@yusukebe Should I prepare an integration inside snippets and you will move it later or should I wait?

[yusukebe]

@schettn

We are working on it. Please wait a bit!

[yusukebe]

Hi @schettn

We've created a new section Examples on our website. I think it's a good place to put your content with Pylon.

How about putting it here?

[schettn]

Hi @schettn

We've created a new section Examples on our website. I think it's a good place to put your content with Pylon.

How about putting it here?

Done! https://github.com/honojs/website/pull/408