-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Condition Widgets trigger hundreds of persistence calls. #5137
Labels
Comments
It looks like this is the offending line of code. There are two issues here -
|
nikhilmandlik
added a commit
that referenced
this issue
Apr 29, 2022
nikhilmandlik
added a commit
that referenced
this issue
Apr 29, 2022
nikhilmandlik
added a commit
that referenced
this issue
Apr 30, 2022
15 tasks
I'm no longer seeing requests from condition widgets |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Summary
Navigating to a condition widget triggers hundreds of persistence calls, despite nothing having changed.
Expected vs Current Behavior
Condition widgets (and indeed all object views) should not be mutating domain objects unless the user has actually changed something. Mutating a domain object will trigger persistence, which is expensive. Do not use mutation to establish an object's default state.
Steps to Reproduce
Environment
Impact Check List
Additional Information
The text was updated successfully, but these errors were encountered: