Gomah / prisma-serverless

Prisma (Nexus) + Typescript + AWS Serverless Lambda = :fireworks:
https://q94zymp1ig.execute-api.ap-southeast-2.amazonaws.com/production
MIT License
117 stars 12 forks source link

chore(deps-dev): bump prisma from 2.22.1 to 2.23.0 #833

Closed dependabot-preview[bot] closed 3 years ago

dependabot-preview[bot] commented 3 years ago

Bumps prisma from 2.22.1 to 2.23.0.

Release notes

Sourced from prisma's releases.

2.23.0

Today, we are excited to share the 2.23.0 stable release 🎉

🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

Major improvements & new features

JSON Filtering is now in Preview

Starting today, you can now filter rows by data inside a Json type. JSON filtering support is available in PostgreSQL and MySQL. You can try it today by adding the filterJson preview flag to your generator block. This has been one of our most popular feature requests, so we're very excited to be getting it into your hands!

To get an idea of how JSON filtering works, let's see how you might query application logs stored in your database. Given the following Prisma schema:

generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["filterJson"]
}

model Log { id Int @​id @​default(autoincrement()) level Level message String meta Json }

enum Level { INFO WARN ERROR }

And the following records in your PostgreSQL database:

id level message meta
2 INFO application listening on port 3000 {"host": "bob"}
3 INFO upgrading account {"host": "alice", "request_id": 10}
4 INFO charging customer {"host": "alice", "amount": 20, "request_id": 10}
5 ERROR credit card expired {"host": "alice", "amount": 20, "request_id": 10}
6 INFO signing up {"host": "bob", "request_id": 1}
7 INFO application listening on port 3000 {"host": "alice"}
8 INFO signed up {"host": "bob", "email": "james@gmail.com", "request_id": 1}

We can now filter logs by the data inside the meta field. Let's query by the request_id inside the meta field to track the journey that led up to the error.

We can write the following query:

... (truncated)

Commits
  • ef2bfe4 feat(client): add JSON filtering to Postgres and MySQL (#7114)
  • 722bdba chore(deps): update dependency @​types/pg to v8 (#7145)
  • c666976 fix(migrate): seed - wait for promise (#7139) (#7144)
  • bc01b9e chore(deps): update dependency @​types/node to v14.17.0
  • 3f855b8 test(client): update napi snapshot (#7141)
  • 488c2b3 fix(tests): Fix napi tests
  • 4369b4a chore(github): remove duplicate question for version from bug form template
  • 47decbd fix(migrate): seed - await exported function (#7139)
  • 2fa7bcc refactor(fetch-engine): cleanup promise of fs (#7132)
  • f0c9a3c fix(client): fix generate output for dot Prisma Client dir (#7134)
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

If all status checks pass Dependabot will automatically merge this pull request.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)