Closed fvet closed 2 years ago
If you remove these actions from "alOutline.codeActionsOnSave" setting, then you can run them manually by moving cursor to object keyword (page/codeunit/table/...) or object name and then clicking on the yellow bulb. These actions should be visible in the menu that will be opened.
Hi
I've released a new version of the extension, it contains a few fixes that should help you with performance issues with large al projects:
We've tried to start fixing some of the code warnings by having variables / properties sorted upon saving the file.
However, AL is acting terribly slow (https://github.com/microsoft/AL/issues/5664) in larger projects (4700+ files) when formatOnSave is enabled (even on files with a few hundred code lines) and it does not seem like we should expect any fixes soon from MS :( Disabling formatOnSave is not the answer we'd expected.
Is there any workaround / better way to have the SortProperties / SortVariables (manually) ran as part of a Code Action, separate commandlet, ... instead of upon saving the file? Right now, we need to wait 10+ minutes untill we then finally decide to cancel the save/format operation.