graphql

[cch5ng]

• migrate over install, configuration
• migrate over the logic (schema, resolvers) from the older repo
  (affects server/index.ts; server/schema.ts)
• handle jobs queries (jobs list by userid and job by id) and mutations (create, edit, delete)
• actually decide whether graphql is actually needed in this case at all (think prisma can handle making the db queries)

still need to conceptualize remix routing

---

resc
https://github.com/prisma/prisma-examples/tree/latest/typescript/graphql-sdl-first
https://www.apollographql.com/docs/react/get-started/

https://www.prisma.io/docs/orm/prisma-schema/data-model/multi-schema
https://www.prisma.io/docs/orm/prisma-schema/introspection

[cch5ng]

X-(done): status is first blocker was fixed
right now there seems to be a bug with retrieving jobs
the existing repo logic has a relationship between user/role/target object (like note) but the job table doesn't have anything like ownerId or role associated currently so no data coming back
in the least believe these tables need contents updated:

• Permission
• _PermissionToRole
• job
• (not sure about verification or if something related to _job_user also needs to change)

[cch5ng]

workaround

apollographql/apollo-client#9976 #issuecomment-1768446694

review this again (perhaps apollo client is not needed for the current setup)

https://github.com/prisma/prisma-examples/blob/latest/typescript/graphql-sdl-first/src/schema.ts

https://github.com/prisma/prisma-examples/blob/latest/typescript/graphql-sdl-first/README.md

https://www.reddit.com/r/nextjs/comments/pree96/next_prisma_do_i_still_need_graphql/