Don't render parts for self-originated changes #52
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 PR includes an experimental change to evaluate the impact of #36, which proposes not rendering parts that update their own options.
First impressions are positive so far- the SlickGrid in particular seems more stable and performant. It seems like the wrapper was written for this execution model, which makes sense considering it's history in the enterprise platform.
We'll need to test a variety of UDPs and dashboards to ensure that this doesn't cause unworkable breakage, and going through the process of fixing UDPs that are broken by this change should tell us more about the real-world, practical impact of this.
Post-experiment To Do
After that's done, there's still some followup before this can be merged onto mainline:
Will fix #36.
Known breakages: