fix(dbgenerated): Fix wording and details around dbgenerated and default #5007
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ay `dbgenerated(...)` to make clear it needs a parameter
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
This PR changes the following pages (Vercel Preview Deploy links): Changed Vercel links
(Note that links will only be valid after Vercel preview deploy succeeded) |
|
This PR probably requires the following redirects to be added to vercel.json:
|
janpio
changed the title
dbgenerated() to always say dbgenerated(...) to make clear it needs a parameterdbgenerated() is not allowed any more
9 tasks
Jolg42
reviewed
Jul 6, 2023
content/400-reference/200-api-reference/100-prisma-schema-reference.mdx
Outdated
Show resolved
Hide resolved
nikolasburk
reviewed
Nov 23, 2023
content/400-reference/200-api-reference/100-prisma-schema-reference.mdx
Outdated
Show resolved
Hide resolved
nikolasburk
reviewed
Nov 23, 2023
content/400-reference/200-api-reference/100-prisma-schema-reference.mdx
Outdated
Show resolved
Hide resolved
nikolasburk
reviewed
Nov 23, 2023
content/400-reference/200-api-reference/100-prisma-schema-reference.mdx
Outdated
Show resolved
Hide resolved
nikolasburk
reviewed
Nov 23, 2023
There was a problem hiding this comment.
- I made suggestions to change the sentence "annotated with a
@defaultvalueattribute" because we're annotating fields with attributes, not values - do we know which release we need to fill in where I left the other comment? if no, maybe just drop that bullet altogether for now so that we can merge this one?
Co-authored-by: Nikolas <nikolas.burk@gmail.com>
nikolasburk
reviewed
Nov 24, 2023
content/400-reference/200-api-reference/100-prisma-schema-reference.mdx
Outdated
Show resolved
Hide resolved
nikolasburk
approved these changes
Nov 24, 2023
janpio
changed the title
dbgenerated() is not allowed any more
|
Yes, please add a link to the PR where you moved the future upcoming breaking change though. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Includes switch of
dbgenerated()to always saydbgenerated(...)to make clear it needs a parameter.Depends on prisma/prisma#19313
This will only be relevant for a future major version that removes
dbgenerated()as a valid value.