mathworks / mathworks/MATLAB-extension-for-vscode
Doesn't support codeAnalyzerConfiguration.json
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 435
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
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 see:
a) VS Code editor shows a single issue. This is one that comes out of the box
b) the Terminal is showing the output of codeIssues on this folder. It shows 4 issues - adding 3 from the configuration
To Reproduce
I've attached a sample repo. It has a single MATLAB code file and resources\codeAnalyzerConfiguration.json:
customCodeIssuesVSCode.zip
- Unzip attachment, open folder in VS Code
cdinto resources, runmatlab.codeanalysis.validateConfigurationStepsto verifycodeAnalyzerConfiguration.jsonis configured correctlycdback to root, runmatlab.codeanalysis.refreshConfigurationto ensure the configuration is applied- Run
c=codeIssues;c.Tableto see the list of issues. You should see four - Look in the editor. Should see four issues, but you will only see 1 (if get the same result as me)
Expected behavior
I expect this to behave the same as desktop MATLAB editor, which I have verified shows the issues. This screenshot is from the same session of MATLAB (launched from VS Code with desktop)
Useful Information
- MATLAB Version: 25.1 (R2025a, Update 1)
- OS Version: macOS 15.6.1
- VS Code Version: 1.102.2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Use the attached sample repository to reproduce the mismatch: run matlab.codeanalysis.validateConfigurationSteps and matlab.codeanalysis.refreshConfiguration, then compare codeIssues output with the VS Code editor diagnostics. Trace the extension's code-analysis integration and determine why configured issues are omitted; done means the editor shows the same four issues as desktop MATLAB.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100