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
Hey! Unsure if this is intended behaviour or not, but I found myself working with a Node buffer today and whenever I tried to access a member of the Buffer class that wasn't there, a notification within vscode will pop up to yell at me, which I feel is a little excessive considering most of the time its a typo on something that I am actively writing and looking at (and thus noticing). The notification pops up the moment the typo happens, barely a pause or anything in between, I didn't even hit save.
To recreate:
import{Buffer}from'node:buffer';constbuf=Buffer.fri// <-- innocent typo when writing Buffer.from
I assume this problem isn't exclusive to Node buffers but that is the case that I ran into and can reproduce 100% of the time.
This is the infamous popup:
This is the error when I hit "Go to output":
This actually somehow breaks through vscode's dnd mode as well as me manually turning off the notifications for deno.
My preemptive apologies in case this is actually a vscode issue and not deno's.
The text was updated successfully, but these errors were encountered:
nathanwhit
added
needs investigation
requires further investigation before determining if it is an issue or not
lsp
related to the language server
bug
Something isn't working correctly
and removed
needs investigation
requires further investigation before determining if it is an issue or not
labels
Nov 8, 2024
Version: Deno 2.0.5
Hey! Unsure if this is intended behaviour or not, but I found myself working with a Node buffer today and whenever I tried to access a member of the Buffer class that wasn't there, a notification within vscode will pop up to yell at me, which I feel is a little excessive considering most of the time its a typo on something that I am actively writing and looking at (and thus noticing). The notification pops up the moment the typo happens, barely a pause or anything in between, I didn't even hit save.
To recreate:
I assume this problem isn't exclusive to Node buffers but that is the case that I ran into and can reproduce 100% of the time.
This is the infamous popup:
This is the error when I hit "Go to output":
This actually somehow breaks through vscode's dnd mode as well as me manually turning off the notifications for deno.
My preemptive apologies in case this is actually a vscode issue and not deno's.
The text was updated successfully, but these errors were encountered: