diff options
| author | Nathan Whitaker <17734409+nathanwhit@users.noreply.github.com> | 2024-04-22 08:03:16 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-04-22 08:03:16 -0700 |
| commit | aac7a8cb7cc675e3cb2ca1ddb39629a8fa59113b (patch) | |
| tree | c7bfff39027d739281b8f666d91023e921a45746 /cli/tools/coverage | |
| parent | 2f5a6a8514ad8eadce1a0a9f1a7a419692e337ef (diff) | |
perf(lsp): Batch "$projectChanged" notification in with the next JS request (#23451)
The actual handling of `$projectChanged` is quick, but JS requests are
not. The cleared caches only get repopulated on the next actual request,
so just batch the change notification in with the next actual request.
No significant difference in benchmarks on my machine, but this speeds
up `did_change` handling and reduces our total number of JS requests (in
addition to coalescing multiple JS change notifs into one).
Diffstat (limited to 'cli/tools/coverage')
0 files changed, 0 insertions, 0 deletions