v0.6.1

Overview

Features

• 68ed3cc feat: add support for latest prisma 2 (#539)
• e870ee4 feat: prevent errors if a wrong field is projected (#535)

Fixes

• ea329e4 fix: when photon import fails, show error instead of assuming

BREAKING CHANGES

• 68ed3cc feat: add support for latest prisma 2 (#539)

  Your app must now depend on @prisma/photon. It is also now a peer dependency of nexus-prisma so you should get warnings that help you do the right thing. But to state it here explicitly:

  npm install @prisma/photon@alpha
  

Highlights

• 68ed3cc feat: add support for latest prisma 2 (#539)

  Support for photon facade package!

• e870ee4 feat: prevent errors if a wrong field is projected (#535)

  nexus-prisma has better support for incremental development when syncing api layer with prisma model changes.

  It used to be that .crud and .model errors would prevent your app from booting. This hindered the inner loop of a development workflow. There should be two benefits you experience in your day-to-day now:

  1. You will see clear domain-specific log warnings in your terminal instead of large generic stack traces/runtime errors. NOTE the old behaviour is still the case in production, because that's what you'd want.

  2. Changes to your Prisma schema often cascade to the API layer in ways that break it, requiring new mapping, type handling, etc. During development you can now still run your server while in a de-synced state, and so take care of the cascading changes incrementally.