-
Notifications
You must be signed in to change notification settings - Fork 2
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
Upgrade Blitz.js and Prisma #25
base: main
Are you sure you want to change the base?
Conversation
- Blitz.js 0.27.1 -> 0.29.7 - Prisma ~2.12 -> 2.15.0 - Updated `prisma migrate` - Modified `prisma-test-environment` to match new breaking changes - Fix some broken pieces of code after upgrade
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/ingenious-agency/mensaje/5sft4792b |
@@ -17,8 +17,11 @@ async function createReaction({ data }: CreateReactionInput, ctx: Ctx) { | |||
}) | |||
if (existingReaction) return existingReaction | |||
|
|||
// Add the user connection to data | |||
data.user = { connect: { id: ctx.session.userId } } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why this instead of spreading? Just curious...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Spookie 👻
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great @Fralez! I think we should backup our DB and deploy after-hours so we don't impact, but it seems this should work.
Great work in this PR btw 👏
prisma migrate
prisma-test-environment
to match new breaking changesWARNING: This PR may break the Production database if merged and deployed.
In order to avoid this, we must baseline our Production environment. This isn't done yet, I'll update when this is finished.
TO DOs