[FIX] Optimize Text Document Change Handling with Debouncing

[musab-mah-7]

Optimize Text Document Change Handling with Debouncing

Summary

This PR introduces a debouncing mechanism to our language server's handling of the textDocument/didChange event. By wrapping the event handler with a debounce decorator, we aim to improve performance and reduce server load by minimizing the frequency of processing rapid, consecutive text changes.

Motivation

In our current implementation, the language server processes every text change event as it arrives. This can lead to performance issues, particularly when handling large documents or when users type rapidly, as it results in unnecessary computation and can overload the server. By introducing debouncing, we ensure that text change events are processed only after a brief period of inactivity (2 seconds), significantly reducing the computational burden and improving the overall responsiveness of our language server.

Changes

• Debouncing Mechanism: Implemented a debounce function that prevents a specified function from being called more than once within a given timeframe (2 seconds for this implementation).
• Application to Text Document Changes: Applied the debounce decorator to the textDocument/didChange event handler. Now, the handler will only be invoked after 2 seconds of inactivity following a text change, instead of on every change.

Expected Impact

• Performance Improvement: Reduced load on the server by avoiding the processing of every single text change event. This is especially beneficial during rapid typing or bulk text operations.
• Enhanced User Experience: Users should experience a more responsive editing environment, especially in scenarios involving large files or complex language features that require significant processing.
• Resource Efficiency: Decreased network and CPU usage, as the number of update operations sent to the server and the corresponding validations or computations are reduced.