SeeRepo with Prisma

Prisma describes your data in a schema file. SeeRepo reads it inside whatever framework your app uses.

What SeeRepo reads

• Your models, from every model X { … } in your *.prisma files. Each one is a data model on your map.
• Who uses them, from your code's Prisma calls, like prisma.user.findMany() or db.post.create() (also through a transaction, tx.…). That's how a cable gets drawn from a part of your product to its data, with reads or writes to.
• Your database as a service, from your packages, your environment variables and the URLs in your code.

An example from our test bank

mehari06/Smart-Resume-Job-Matching-System, a Next.js app with Prisma, read at a fixed commit:

• 11 data models from prisma/schema.prisma: Account, ActivityLog, Application, Job, JobReport, Match, Resume, Session, User, UserReport and VerificationToken
• 22 screens, 20 actions and 2 API doors
• Sentry, Postgres and Google, found as services with their proof

Good to know

• Only the schema's model blocks become data models: enums and views don't.
• Drizzle, another way to describe data in TypeScript, isn't read yet.