-
Notifications
You must be signed in to change notification settings - Fork 367
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
[SDK-3582] Use form-encoded data by default #945
Conversation
f89f17d
to
967da7f
Compare
src/global.ts
Outdated
* **Note:** If you are using Auth0 rules and are sending custom, non-primitive data make sure to verify that your Auth0 Rules continue to work as expected. If they do not, | ||
* then set this to `false`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know this was discussed in an earlier review, but seeing this now makes me wonder if this note should be rephrased still, or left out alltogether.
It used to be a note that referred to anyone touching this value. Which means, as long as people didnt change the value of useFormData
, the note was irrelevant.
Now, the note is relevant to anyone not setting the value instead.
I think we can drop the note, but ensure we call it out in the migration guide before we release v2. What do you think?
This prevents an error being logged when running the dev server via npm start Co-authored-by: Frederik Prijck <[email protected]>
44eb7f6
to
c1bd290
Compare
Changes
Updates the
useFormData
property to now default to true. Consequently, updates any tests whereuseFormData: true
was previously set to now use the default, and setsuseFormData: false
where the assertions on the testcase indicate it should be.Checklist