Closed m4tty-d closed 2 years ago
Hey! I had the same problem today so I little bit dive into the problem.. I think the main problem is in mix of ra-core versions
Let me know!
I am also experiencing this issue. Will try to dig into the problem.
downgrade ra-data-graphql to v3.11; immediately after that version, there was a complete refactor https://github.com/marmelab/react-admin/commit/59742f5297a3c28af8c0882fad53c01bd4bab511
I am getting the same issue with v4 typegraphql-prisma and ra-data-prisma.
hey guys, can you all provide which versions you use of react-admin, ra-core and ra-data-prisma
@chrisschaub notice, the error in this issue is related only to the dataprovider, means the frontendpart and therefore has nothing to do with typegraph-prisma
we maybe should no longer rely on ra-data-graphql 🤔
downgrade ra-data-graphql to v3.11; immediately after that version, there was a complete refactor marmelab/react-admin@59742f5
seems they did not mark it it properly as a breaking change. We can therefore lock the the version or use the new version
should be fixed now in newest version (stable v6.9.1 or beta v7.0.0-beta.2)
I'm trying to use the latest version of
@ra-data-prisma/dataprovider
with a typegraphql backend. (crud generated from a prisma schema)My component looks like this:
When I try to open it in the browser, I'm getting the following error in the console:
I get the same error with and without TS in a brand new CRA app.
I also tried to roll back to the previous version with no luck. :(
Do you guys have any idea what could be the problem?