improve how we calculate when to summarize flutter errors #4447
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.
Instead of deciding to summarize errors subsequent to the first error after a reload, we instead summarize errors subsequent to the first error after a frame event. Those errors are more likely to be errors (overflow, ...) triggered by the first error.
From the flutter error sample app, navigating to the material error, then the overflow error, you can see now that the overflow triggered by the material error is summarized, but the later overflow from the overflow page is not.
...