docs: use the new pgTable signature instead deprecated #433
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
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.
Since drizzle-orm 0.36.0, the
pgTable(name: ..., columns: ..., extraConfig: (...) => PgTableExtraConfig)API is deprecated andpgTable(name: ..., columns: ..., extraConfig: (...) => PgTableExtraConfig[])API has been introduced.https://github.com/drizzle-team/drizzle-orm/pull/3193/files#diff-8cc5eab297b00bd8fd753c57063cc3dd441af6c96b23dba32df67e0acfe3f961
So this pull request amends the docs, to guide to use the latest API.
If there are code style conventions to use, please let me know. Because there is no source about it (e.g.,
CONTRIBUTING.md), I amended the example codes returnarraywithout other changes.