Fixing frequent re-renders with latest app-lib-dotnet
#2683
+59
−26
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.
Description
In the latest
app-lib-dotnet
, the backend sends us updated instance data after saving form data. Great stuff, which will fix some issues we've had, but this made some of our greedy selectors re-render components too often, which also at some point caused duplicate components to show up in a repeating group (because the node hierarchy got forcefully re-rendered). This fixes the root cause, but later I'll also open a PR with a fix that makes sure that exact thing cannot happen again even despite re-rendering.Related Issue(s)
Verification/QA
kind/*
label to this PR for proper release notes grouping