feat: support custom field attributes in plugin schemas #5330
+23
−4
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.
In the auth config, you can define a user/session/account/etc schema to customize the field attributes in a given table.
Right now with plugin schemas, you can only customize the field name. With this PR, will allow support for customizing any field attribute of the field, not just field name.
For example, in the Username plugin, you can't enforce the
username
to be required. With this PR you can do so:Please merge the following PR after this is merged:
#5323
Summary by cubic
Enable plugin schemas to override any DB field attributes, not just rename fields. This lets plugins enforce constraints (e.g., required username) via auth config while staying backward compatible.
New Features
Migration