Summary

Let's end our journey with Pylon by summarizing what we have learned so far.

First, we implemented our logic through a class, whose methods we passed to Pylon as a singleton instance. Then we looked at a simpler approach, where we placed independent functions into a .ts file and passed them to Pylon afterward.

In addition, we looked at how we can incorporate different types of data sources (Hardcoded Data, External API, and Database with Prisma).

All these points have shown that Pylon does not impose any restrictions on how we structure our code, and we can tap into different data sources in any way we want.

In the end, Pylon allows us to build our project like any other. We only need to inform Pylon which functions should be available as queries or mutations in our GraphQL interface. Pylon does not require us to follow any particular code principles. The only important thing is to have enough type safety, as Pylon requires this to automatically build a GraphQL schema from the provided types.