Collect feedback on desired examples for the 'examples' folder

[productdevbook]

We are planning to create an 'examples' folder in this repository and want to gather feedback from users about what kinds of examples would be most useful.

Please comment below with:

• The type of example you would like to see (e.g., integrations, sample queries, real-world use cases, etc.)
• Any specific problems or scenarios you'd like to see covered
• Other suggestions for improving example content

Your input will help us create better, more relevant examples. Thank you for your feedback!

[nhattran998]

Thank you @productdevbook . Here is the request people need for those who want to apply Nitro GraphQL to projects.

1. Better auth basic + Google --> Inject into h3/hono/elysia instance(can pick h3 first, then hono, can decide following the most popular + community supports plugins). I prefer "hono" first because the Hono Middleware was really good
2. Nitro Node/Bun/Clouflare --> React/Vue GraphQL + TS Query/Pinia Query
3. Nitro GraphQL combined with Tanstack Start with React -- Nuxt with Vue
4. In the HTTP layer, it can be switched to Hono/Elysia/Express/Fastify if they want + can customize the routes.
5. Provide real-time subscriptions examples with Fetch/Query
6. Detail more custom directives like "hasPermission" with real cases of RBAC, ACL
7. Integrate with BE like Postgres/SQLite with Prisma/Drizzle/MikroORM--> Have resolvers, repository, services... like a professional project -- I might be able to help with this because I need this in the following week
8. Integrate with Zod/Valibot validation schema
9. Auto-generate guards typing for "__typename" like you did for the "user" module in the playground folders.
10. Nowadays, AI hype can boost any project, and can integrate this with Vercel AI SDK examples to do AI things 😆

Quite a list, lah. I just wanted to say "thank you for this project" and discuss it further with you.

[productdevbook]

drizzle-orm + zod example

[nhattran998]

@productdevbook About the Drizzle ORM + Zod examples, here is the feedback

1. Should inject the database into the context of graphql resolver. Graphql yoga had an option "context" .

Here is an example of my current application with Yoga config

   const yoga = createYogaApp({
      contextFactory: async (req: YogaInitialContext) => {
        await graphqlRoleGuard(c, req) // Handle permissions

        return {
          logger: c.get("logger"),
          database: c.get("database"),
          requestId: c.get("requestId"),
          userAgent: c.get("userAgent"),
          location: c.get("location"),
          ...(c.get("user") && { user: c.get("user") }),
        } as GraphQLAuthContext | GraphQLGuestContext
      },
    })

Then on each resolver, you can do this

export const bookQuery = defineQuery({
  // Get a single book by ID
  book: async (parent, { id }, { database }) => {
    const result = await database.select().from(book).where(eq(book.id, id))
    return result[0] || null
  },
})

2. The file naming should be more clearer like graphql-yoga.config.ts examples/drizzle-orm/server/graphql/config.ts. In case the user uses "appolo" --> graphql-apollo.config.ts. Because in our applications, we have a lot files like config.ts.
3. Should add a "examples/drizzle-orm/docker-compose.local.yaml" for development only, exclude the "app" service.

[productdevbook]

better-auth example

[productdevbook]

@harrytran998 I'm thinking about how to get Hono/Elysia's support. We'll get to her. Changes are needed in the core.

[nhattran998]

@harrytran998 I'm thinking about how to get Hono/Elysia's support. We'll get to her. Changes are needed in the core.

@productdevbook Yes. It should be like that. Because in my case, our codebase uses Hono as an API(it is backed by Cloudflare, and the community is really active). You can consider borrowing/collaborating with the Vike Team about Universal Middleware. Like the way the user can switch yoga/apollo.

Zod Schema + Drizzle ORM

The weirdest things already configured use Yoga. But when I open the playground --> still Apollo Playground 🧑‍🍳.

Better Auth + Drizzle ORM

1. In [examples/better-auth/server/graphql/auth/auth.graphql] --> The query me has auth directive, but in the [me resolver](examples/better-auth/server/graphql/auth/queries/me.resolver.ts) --> You still need to casting type ✌🏻 So question is could we detect where the field have auth directive --> the user variable will typesafe?
2. In the middleware folder, could we follow the best practice of Nitro middleware? like order number. 01.session.middlware.ts
3. In the examples/better-auth/server/routes/api/auth/[...all].ts and middlewares/session.ts --> Still import directly better-auth from file. Could we inject it into h3 event? And can pass it into graphql context in case we want to use auth related features in another module.

[productdevbook]

"The weirdest things already configured use Yoga. But when I open the playground --> still Apollo Playground 🧑‍🍳."

The reason for this is that I added it by default. The game area was going very well. But this needs to be changed in the nitro configuration.