diff options
author | Veetaha <[email protected]> | 2020-08-08 19:53:38 +0100 |
---|---|---|
committer | Veetaha <[email protected]> | 2020-08-08 19:53:38 +0100 |
commit | e43811c1645f78818d5d7fe0054b54a462145847 (patch) | |
tree | 43c7e67da3e783af3f06033478d306a2cfc99490 /crates/vfs-notify/Cargo.toml | |
parent | a69f19a6a5899bdfb6fc498371650bf54263deff (diff) |
Fix no inlay hints / unresolved tokens until manual edit
No we return ContentModified during the workspace loading. This signifies the language
client to retry the operation (i.e. the client will
continue polling the server while it returns ContentModified).
I believe that there might be cases of overly big projects where the backoff
logic we have setup in `sendRequestWithRetry` (which we use for inlay hints)
might bail too early (currently the largest retry standby time is 10 seconds).
However, I've tried on one of my project with 500+ dependencies and it is still enough.
Diffstat (limited to 'crates/vfs-notify/Cargo.toml')
0 files changed, 0 insertions, 0 deletions