Pulse Type
Is there a good way to get the type of a Prisma Client instance with Pulse before instantiating it?
For context, I have a class that will eventually have a member populated with a Pulse DB instance:
10 Replies
Currently I'm doing this to get that type but am not sure if this is a good way to do it:
Hey @Sabin Adams 👋
Hope you are doing great! 🙂
Your approach looks good. I am not aware of any other way.
An alternative you may consider is doing something like:
Thanks!
The
ReturnType
approach is my go-to for getting the type of any extended Prisma Client. Let us know what you think of Pulse 😉Thanks! It’s powering my dbchange service that keeps the db and Algolia in sync 😁
No problems so far other than spending a bunch of time with different db’s trying to get it to work with pulse. A lot of the docs and integrations seemed out of date
Finally got it working with Supabase (not sure how, just started working 🤷🏻)
A lot of the docs and integrations seemed out of datePrisma docs or database vendor docs?
Prisma docs
Hey @Sabin Adams 👋🏾 , hope you're doing well 😃 !
A lot of the docs and integrations seemed out of dateCould you share which part of the docs did you find out to be outdated 🙏🏾 ?
Mostly the integration docs for Pulse. Specifically for Neon and Railway. The Railway integration doesn’t run (unless I goofed) and the Neon UI is different from what’s shown in the docs
I can give more specifics when I’m at a computer 😅
For the record, once I got things working it’s been seamless :heart:
Thanks @Sabin Adams !