Open alexdewar opened 5 days ago
I think such a change can improve user experience if implemented along with configuring the Code Analyzer.
-plan(task) = CodeIssuesTask;
+plan(task) = CodeIssuesTask(WarningThreshold=0, Configuration='codeAnalyzerConfiguration.json');
The manually configured Code Analyzer could prevent unhelpful or unwanted warnings during CI checks and regular work on the project.
While there is a GitHub Action to check for errors in code, it is not currently checking for warnings, which could be useful. The only caveat is that if Matlab produces a lot of unhelpful warnings, failing the CI for every single one is probably not that useful. I haven't actually used it recently enough to know whether this is likely to be a problem or not though.
In order to check for warnings too, you'll need the following change: