You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The protocol defines quite some message which are executed on a text document (e.g. folding ranges, document links, colors, ...). Clients usually send these request after a timeout ask the server to recompute the responses after the user typed. Since these request require to reconcile the AST and even may be resolving symbols it would be useful for a server to know that a client will ask for on of these requests. To support such an optimization we should look into batch n requests. Two ideas:
have special LSP level notifications for this. This is comparable to begin/end transaction in DBs.
The protocol defines quite some message which are executed on a text document (e.g. folding ranges, document links, colors, ...). Clients usually send these request after a timeout ask the server to recompute the responses after the user typed. Since these request require to reconcile the AST and even may be resolving symbols it would be useful for a server to know that a client will ask for on of these requests. To support such an optimization we should look into batch n requests. Two ideas:
The text was updated successfully, but these errors were encountered: