Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Deprecate tuple-based pgJwtType and use Postgres-parser-based pgJwtTypes instead #434

Merged
merged 3 commits into from
Jul 28, 2023
Merged

Deprecate tuple-based pgJwtType and use Postgres-parser-based pgJwtTypes instead #434

merged 3 commits into from
Jul 28, 2023

Conversation

benjie
Copy link
Member

@benjie benjie commented Jul 28, 2023

Fixes #430

@benjie
Deprecate tuple-based pgJwtType and use Postgres-parser-based pgJwtTy…
8065572 
…pes instead.
@benjie
docs(changeset): Deprecate preset.gather.pgJwtType (tuple), instead…
a9561d6 
… use `preset.gather.pgJwtTypes` which expects a string and parses it similar to the PostgreSQL parser (and also allows multiple types to be specified).
@benjie benjie added this to the V5 beta milestone Jul 28, 2023
Base automatically changed from yet-more-docs to planning July 28, 2023 12:11
@benjie benjie merged commit e639a53 into planning Jul 28, 2023
1 check passed
@benjie benjie deleted the pg-jwt-types branch July 28, 2023 14:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
V5 beta
Development

Successfully merging this pull request may close these issues.

pgJwtType should be a string with a proper parser not an array.
1 participant
@benjie