feat: custom payload properties for registration #218
Merged
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.
PR to implement the feature proposed in issue #189.
Types of changes
Description
Added the possibility to add custom user fields to the registration payload.
[field: string]: string | number | boolean | object | Array<string | number | boolean | object>
The types
string
,number
,boolean
andobject
together with the same types as an array should cover all possible fields in Strapi.I also checked if the register endpoint can somehow handle FormData (spoiler, it doesn't) to add a profile picture on registration. But since this would be a custom change to a Strapi controller, it's not really needed here.
Furthermore I added the
cas
authentication provider which I found in this tablist and the possibility to add a custom provider string, as it is possible to add custom providers to Strapi.Finally, I went through all pages of the documentation and just verified / corrected links which point to a certain line of code. I also corrected the register example which used
identifier
&password
as payload properties and added thephoneNumber
property as an example.Checklist: