Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

@deprecated for relation fields #227

Open
kasir-barati opened this issue Dec 5, 2024 · 1 comment
Open

@deprecated for relation fields #227

kasir-barati opened this issue Dec 5, 2024 · 1 comment

Comments

@kasir-barati
Copy link

So I read this issue: #104

But my case is something like this:

model User {
  /// @deprecated use userProfile instead
  profile @relation(fields: [profileId], references: [id])
  
  // BUT we cannot defined same relation twice in Prisma!!!
  userProfile @relation(fields: [profileId], references: [id])

  profileId String!
}

Any comment on this?

@kasir-barati
Copy link
Author

Also if we do not have any other solution except rolling this breaking change out suddenly, that then goes against one of the core concepts of GraphQL which is giving our client time to adapt to new API and remove something when nobody is using it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant