TEST / DEBUG PR: Submission save+sub stability / performance #4214
+176
−17
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.
This is NOT a PR ready for merge, it is an early look at some experimentation I have been doing with debouncing of save dispatch actions, and more thorough subscription management / tracking to reduce the computation overhead and increase the stability of the submission service and form component.
I invite any testing, comments, reviews - one useful exercise is to keep the debug logging in but reverting the other changes and comparing the numbers of logged events. The work here shows a clear improvement, I think, but more work is needed.
I'm leaving the console output, commented-out lines in for now to help see alternatives and changes, and for live testing help.