65
When developing in a big workspace and/or in a big single-folder solution it is not always helpful to have the code analyzed as You go.
- Code Analysis will often be slow to react
- Code Analysis will be surfacing errors and warnings not related to what You are actually doing at the moment

So the suggestion would be:
- Introduce a command to stop analyzing, also clearing the analysis cached and displayed so far
- Introduce a command to resume analyzing, analysis to start from the active al-file to identify the active extension
Category: Development
STATUS DETAILS
Completed
Ideas Administrator

Thank you for your feedback. We have been investing a lot in the code analyzer framework this upcoming 2023 release wave 1. You can already try it out in the Preview release.

We have optimized when rules are run, fixed some inefficiencies, and disabled rules no longer run…

We have also introduced a new “File” scope for code analysis during authoring , so that code analysis now runs on the active file only by default. This provides much better .performance during coding with, and most rules rely on local analysis anyway. You can still enable rules to run on project level, as they also all run on full build

The benefits are that workspace size does not prevent the use analyzers​ and thus analyzers can be enabled in larger apps and used for everyday work, and you do not need to wait on the CICD pipeline build for CodeCop errors.​

In addition, we've added a new code analyzer performance statistics output, you can enable it via the `outputAnalyzerStatistics` setting. This provides a summary of time spent per rule. Use it to discover which rules are actually running, as well as low-performing rules, in order to enable/diable rules during authoring.

On a related note, you can now also use urls in al.ruleSetPath as well as in includedRuleSets path in the the ruleset file. This makes it easier to share, maintain and enforce common rules

Best regards,
Business Central Team

Comments

R

Would be very helpful in de-clottering the problem pane, until you're finished with basic coding

Category: Development

R

To increase performance it will be nice if the analyzer stop recalculating the "errors" every time I open a file

Category: Development