You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 2, 2022. It is now read-only.
Deploying service `r-2796` to stage `dev2` to server `local` 104ms
Changes:
Category (Type)
+ Created field `projects` of type`[Relation!]!`
Project (Type)
~ Updated field `category`
Category (Relation)
- Deleted relation between undefined and undefined
Category2 (Relation)
+ Created relation between Category and Project
Applying changes (19/5) ⣟
Expected behavior
The deployment goes through. The relation was renamed.
Versions (please complete the following information):
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Describe the bug
When adding an implicit backrelational field and changing the relation name at the same time, the deployment will be stuck.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The deployment goes through. The relation was renamed.
Versions (please complete the following information):
prismagraphql/prisma:1.13
Additional context
Originally reported here: #2796. Added to #2018.
The text was updated successfully, but these errors were encountered: