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
- 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
STATUS DETAILS
Completed
Comments
Would be very helpful in de-clottering the problem pane, until you're finished with basic coding
Category: Development
To increase performance it will be nice if the analyzer stop recalculating the "errors" every time I open a file
Category: Development
Business Central Team (administrator)
Business Central Team