lsp bug?
Is there any reason why intellisense would identify the type correctly, but after completion it would be treated as any? is this a bug with deno? Type should be as intellisense shows.
2 Replies
Based on the documentation, Deno's Language Server Protocol (LSP) has been continuously improved and stabilized over several releases. However, it's possible that you might encounter some issues as it's a complex feature. If you're experiencing a discrepancy between the type identified by IntelliSense and the type treated after completion, it could potentially be a bug.
To help us understand and address the issue, could you provide more details about the problem? Information about the Deno version you're using, the code snippet where the issue is occurring, and the expected vs. actual behavior would be very helpful.
Also, please make sure you're using the latest version of Deno and the Deno VSCode extension, as many issues are resolved in newer versions. If the issue persists, I would recommend reporting it on the Deno issue tracker on GitHub. The Deno team appreciates feedback and bug reports from users to improve the system. 🦕
Can you open an issue about it?