Michelle Hirsch

"View Problem" jumps to first code issue

3

When mousing over code with a code analyzer issue, there's a dialog under the message that offers to View Problem or Quick Fix ... Clicking on View Problem (or using...

Quick Fix doesn't work via keyboard shortcut

2

When mousing over code with a code analyzer issue, there's a dialog under the message that offers to View Problem or Quick Fix ... Clicking on Quick Fix gives a...

Loop highlighting

2

It would be great to get loop highlighting like in the MATLAB editor, so that (for instance) when you select "else" the corresponding if and ends are highlighted. Right now,...

Release distributions don't include license file

1

The MLTBX, which is the primary distribution vehicle for this toolbox, doesn't include the license file. The license is only available for users who download the entire repo, not installation...

Use Project Path instead of manually adding buildUtilities

1

buildplan.m manually adds buildUtilities to the path in your custom tasks. Instead, you can include buildUtilities in the project path and just open the project. It looks like buildtool will...

Simplify packageToolbox by using ToolboxOptions

3

packageToolbox looks more complicated than it needs to be. Use ToolboxOptions to specify the location of the released MLTBX instead of trying to find it and move it: opts =...

Doesn't support codeAnalyzerConfiguration.json

1

**Describe the bug** The VS Code extension doesn't seem to honor custom codeAnalyzerConfiguration.json. Maybe this is user error, but I think I've done everything right. In this screenshot, you can...

Publish the extension to the Open VSX Registry

2

**Is your feature request related to a problem? Please describe.** There are an increasing number of popular forks of VS Code, including Cursor, Windsurf, and Positron. There are restrictions against...

I'm trying to install a bunch of stuff. It's hard to know how the progress is going, other than checking the log file after things fail. It would be nice...