I have a bunch of JavaScript in a project, and occasionally mistype a variable name or something.
VS Code notices this, and puts an itsy bitsy teeny weeny yellow polka dot underline under the first letter of the typo. It is well nigh invisible at the magnification I use on my laptop.
These do not show up on the problems panel, and I haven't figured out a way to search for them. F8 only goes to items that show up on the problems panel -- errors, warnings, and infos.
How do I find these things? If I have to rub my nose on the monitor and squint over every single letter of my JS code, I'll find the typos without the underline.
I have a bunch of JavaScript in a project, and occasionally mistype a variable name or something.
VS Code notices this, and puts an itsy bitsy teeny weeny yellow polka dot underline under the first letter of the typo. It is well nigh invisible at the magnification I use on my laptop.
These do not show up on the problems panel, and I haven't figured out a way to search for them. F8 only goes to items that show up on the problems panel -- errors, warnings, and infos.
How do I find these things? If I have to rub my nose on the monitor and squint over every single letter of my JS code, I'll find the typos without the underline.
For the visibility motivation, see How do I change the color or size of the code suggestion dots that show up under VS Code hints?.
As for navigation controls, I'm not aware of such functionality built in to VS Code. These are called "Editor Hints" and if I understand correctly, they are a severity level of diagnostic that is treated differently than the others. Unlike error, warning, and info, it's rendered differently (dots under one character rather than a whole line of squigglies), and don't get included in the "Go to Next Problem" command. I did a quick issue ticket search and didn't find any existing issue tickets, so I might suggest that you raise a feature request issue ticket asking specifically for command support for navigating between them- either in the existing command or a new one for navigating between these editor hints (but be clear in your description that you're not talking about hovers or inlay hints or other features; a screenshot and the API link I gave earlier will help), and for a view where you can see all of them (maybe the ability to include them in the Problems Panel, where all the other severity levels of diagnostics are shown).
For some side context, you might want to link to Go to next error/warning/info #105795 just for a curious reader's sake, but that only covers errors, warnings, and info, and not hints. A workaround extension for that is in Mark's answer to How do I go to the next error (not next problem) in VS Code using a keyboard shortcut?, but it doesn't look like that extension covers Editor Hints either.