-
-
Notifications
You must be signed in to change notification settings - Fork 46
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.
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
UserAuthCard doesn't format the form body traits correctly #93
Comments
Hey @JacobMillward Have you gotten errors form Ory Kratos when submitting the registration payload provided by Ory Elements? I believe Ory Kratos flat maps the object when giving the ui form fields. For example: {
traits: {
email: string
}
} will become |
Yup I did. Kratos kept giving back the error that the email could not be empty.
|
Hmm interesting 🤔 |
Sure. It's the example from the kratos helm configuration page
|
The format for bodies with traits dictates that the traits come in through their own object. This becomes especially visible when using an SDK client compiled with a newer version of OpenAPI generator, as they only process properties which are defined in the API schema, which is not the case for flattened properties. Fixes ory#93
The format for bodies with traits dictates that the traits come in through their own object. This becomes especially visible when using an SDK client compiled with a newer version of OpenAPI generator, as they only process properties which are defined in the API schema, which is not the case for flattened properties. Fixes ory#93
The format for bodies with traits dictates that the traits come in through their own object. This becomes especially visible when using an SDK client compiled with a newer version of OpenAPI generator, as they only process properties which are defined in the API schema, which is not the case for flattened properties. Fixes ory#93
The format for bodies with traits dictates that the traits come in through their own object. This becomes especially visible when using an SDK client compiled with a newer version of OpenAPI generator, as they only process properties which are defined in the API schema, which is not the case for flattened properties. Fixes ory#93
The format for bodies with traits dictates that the traits come in through their own object. This becomes especially visible when using an SDK client compiled with a newer version of OpenAPI generator, as they only process properties which are defined in the API schema, which is not the case for flattened properties. Fixes ory#93
Preflight checklist
Describe the bug
When submitting the a registration form using
UserAuthCard
, thebody
object returned to the callback on theonSubmit
prop formats the object incorrectly.What is expected is:
What is given is:
This means that unless care is taken, form values are not passed up to kratos correctly.
Reproducing the bug
onSubmit
callbackRelevant log output
No response
Relevant configuration
No response
Version
0.0.1-beta.3
On which operating system are you observing this issue?
Other
In which environment are you deploying?
Kubernetes with Helm
Additional Context
No response
The text was updated successfully, but these errors were encountered: