-
Notifications
You must be signed in to change notification settings - Fork 2.3k
fix: Call latest onChange #1755
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
Conversation
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.
Thanks! Can you add a test, ideally something that exercises exactly the issue described in #1708?
0930a0b
to
9ba4c3a
Compare
@epicfaace Added a test. It was I bit tricky to trigger the condition for the |
This is still valid, I just haven't reviewed it yet. |
- Reimplement two fixes related to `onChange` in the new `Form.tsx` - rjsf-team#1755 fixes the calling of the proper `onChange` during props update - rjsf-team#2460 fixes race condition on calling `onChange` after setState.
- Reimplement two fixes related to `onChange` in the new `Form.tsx` - rjsf-team#1755 fixes the calling of the proper `onChange` during props update - rjsf-team#2460 fixes race condition on calling `onChange` after setState.
- Reimplement two fixes related to `onChange` in the new `Form.tsx` - rjsf-team#1755 fixes the calling of the proper `onChange` during props update - rjsf-team#2460 fixes race condition on calling `onChange` after setState.
- Reimplement two fixes related to `onChange` in the new `Form.tsx` - rjsf-team#1755 fixes the calling of the proper `onChange` during props update - rjsf-team#2460 fixes race condition on calling `onChange` after setState.
…sf-team#3052) - Reimplement two fixes related to `onChange` in the new `Form.tsx` - rjsf-team#1755 fixes the calling of the proper `onChange` during props update - rjsf-team#2460 fixes race condition on calling `onChange` after setState.
Reimplemented in v5 beta due to typescript conversion via #3052 |
Reasons for making this change
Fixes the issue described in #1708
Checklist