47ng/prisma-field-encryption

Detect invalid custom cursor fields

franky47 opened this issue · 1 comments

franky47 commented

When specifying a custom cursor field for the migrations to iterate upon, make sure (and throw error if invalid) that the field is:

  • @unique
  • of type Int or String
  • not @encrypted itself
github-actions commented

🎉 This issue has been resolved in version 1.2.0 🎉

The release is available on:

Your semantic-release bot 📦🚀