Open pushred opened 5 years ago
Have the exact same issue. Is there a solution to this?
Same here. Would be very grateful for a solution on this issue.
Same here
Has anyone on here made any progress? Does writing the mutation work?
I have tested different versions of the prisma docker image, and here is what I found out:
I'm using the 1.34.6 version now, and the admin dashboard is working fine.
I'm also encountering this issue in 1.34.10 with two relational tables:
type User { id: ID! @id contactId: String! @unique email: String! @unique firstName: String! lastName: String! registrationToken: String @unique registrationTokenExpires: DateTime passwordResetToken: String @unique passwordResetTokenExpires: DateTime webhookClients: [WebhookClient] @relation(name: "WebhookClientsUsers") createdAt: DateTime! @createdAt updatedAt: DateTime! @updatedAt }
type WebhookClient { id: ID! @id tagId: Int! deliveryUrl: String! isActive: Boolean! clientUsers: [User] @relation(name: "WebhookClientsUsers") createdAt: DateTime! @createdAt updatedAt: DateTime! @updatedAt }
The Prisma UI will allow me to add webhookClients to a User or clientUsers to a Webhook but won't allow me to save those changes, displaying the "Cannot read property 'split' of undefined" javascript error.
I've tried going from 1.34.10 back to 1.34.6, but now the admin hangs forever at loading...
.
Maybe something internal isn't backwards compatible.
Going back to 1.34.10 I can load the admin again.
Have you tried clearing the browser's local storage and doing a shift+f5 (Ctrl+f5 on Firefox)?
On Wed, Feb 19, 2020, 07:44 Chris Sattinger notifications@github.com wrote:
I've tried going from 1.34.10 back to 1.34.6, but now the admin hangs forever at loading....
Maybe something internal isn't backwards compatible.
Going back to 1.34.10 I can load the admin again.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/prisma/prisma-admin-feedback/issues/158?email_source=notifications&email_token=AAXTBKSWVQJ5PRNH4CZIX23RDUEPTA5CNFSM4IUJCZO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMHI33Q#issuecomment-588156398, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAXTBKRUEETF3AIZI4QA7GLRDUEPTANCNFSM4IUJCZOQ .
Stil the problem not resolved ?!
same here :( version 1.34.6 works for me...
I have similar issue even with 1.34.6 version I am just frustrated with it any fix ?
@musbenlahrech if you are using v1.34.6 try clearing the browser's local storage and doing a shift+f5; Your browser might be using old cached prisma admin files and/or data.
But still, I think this project should be open-sourced. I have tried finding the prisma admin source code, but seems to not be available anywhere. The developers don't seem to be paying enough attention to solve small issues like this. We could solve a bug like this easily if we had access to the code.
@musbenlahrech if you are using v1.34.6 try clearing the browser's local storage and doing a shift+f5; Your browser might be using old cached prisma admin files and/or data.
I could load it but sometimes create doesn't work with nested data
But still, I think this project should be open-sourced. I have tried finding the prisma admin source code, but seems to not be available anywhere. The developers don't seem to be paying enough attention to solve small issues like this. We could solve a bug like this easily if we had access to the code.
Yes definitely, it's is a really important part of the stack since it saves a looot of time and it's why we picked prisma from the beginning.
@musbenlahrech if you are using v1.34.6 try clearing the browser's local storage and doing a shift+f5; Your browser might be using old cached prisma admin files and/or data.
I could load it but sometimes create doesn't work with nested data
Creating nested data does not work for me either. I need to create each part individually otherwise an error occurs.
Maybe related to #120 but opening a new issue because the exception is different: