What it is responsible for
Posts manages post-facing GraphQL operations through PostsModule, with work entering the subsystem there. PostsResolvers groups Query, Mutation, and Subscription members, including posts, post, createPost, updatePost, deletePost, and postCreated. The GraphQL types Post, NewPost, and UpdatePost name the data shapes involved in those operations. PostsService is the service named within the subsystem.
What it needs, and who needs it
Posts depends on sample/22-graphql-prisma/src/prisma; its Prisma-side dependency is required by this subsystem, although the supplied evidence does not identify individual symbols or failure behavior for that dependency relationship. The named sample consumer depends on Posts, so it needs PostsModule as the subsystem entry point and its exposed GraphQL members such as posts and createPost. Without Posts, sample loses that dependency; without Prisma, Posts loses its declared dependency.
15 entities in sample/22-graphql-prisma/src/posts. 1 other subsystem depends on it, which makes it the 11th most depended-upon part of this codebase.
What it is made of
Its 15 entities sit in 4 files under sample/22-graphql-prisma/src/posts: 6 graphql types, 3 graphql mutations, 2 graphql querys, 1 module and 3 more.
schema.graphql holds 12 of them — more than any other file here.
PostsResolvers declares 6 methods, the widest surface here.
Where work enters
PostsModule—sample/22-graphql-prisma/src/posts/posts.module.ts:6
Boundaries
1 other subsystem depends on this one — Sample. Changing what it exposes changes them.
They hold 1 edge into it between them. 2 edges leave it against 1 arriving — it reads more of this repository than this repository reads of it. What they reach is narrower than the folder: 1 of its 15 members carries every inbound edge — PostsModule (1).
It depends on Prisma, and on nothing else in this repository.
Was this page helpful?