Skip to content

good first issue: typo in Prisma schema — myPlaground should be myPlayground (schema.prisma:31) #141

Description

@piyushdotcomm

Bug Description

In prisma/schema.prisma at line 31, the relation field for a user's playgrounds has a typo:

model User {
  ...
  myPlaground Playground[]   // <-- typo: "Plaground" instead of "Playground"
  ...
}

myPlaground is missing the letter "y" — it should be myPlayground.

Impact

  • Developer confusion: Contributors looking for the playground relation on User will search for myPlayground and not find it, leading to wasted debugging time.
  • API inconsistency: Any code referencing user.myPlaground inherits the typo, making the codebase harder to read.
  • Schema evolution: The typo will be propagated to any future Prisma migrations, making it harder to rename later.

Fix

In prisma/schema.prisma line 31:

-  myPlaground Playground[]
+  myPlayground Playground[]

Note: Since this is a MongoDB datasource and not a relational SQL database, renaming a Prisma relation field does not require a migration — it only affects the generated Prisma Client. The fix is low-risk.

After fixing the schema, run:

npx prisma generate

And update any application code that references user.myPlaground to use user.myPlayground.

Files Affected

  • prisma/schema.prisma line 31
  • Any code that accesses user.myPlaground (search codebase)

Difficulty

Good first issue — simple typo fix.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workinggood first issueGood for newcomersgssoc26level:beginnerBeginner level task for GSSoCmaintenanceCodebase maintenance and cleanup

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions