I have been blogging a few times about the Diagnostic Descriptors we get when enabling code analysis. Well – yet again, we have new ones. But I’m not going to keep updating these rulesets, as Microsoft is now doing that on docs. So let me give you one more overview, and the resources to the pages on docs per analyzer.
Now I decided to create a small module that will help you manage the Extensions and Ids.
Besides what I showed in the first post, I added to the module an extra feature: now you have the possibility to get the free Ids: if for example you have 2 table extensions with Ids 50251 and 50254, the free Ids are considered the ones not used within the ones used, so in this example: 50252 and 50253. You can do this by specifying and extra parameter to the function.
Time for the next round of functionality I added in my VSCode Extension (the CRS AL Language Extension) – a functionality that manages your filenames (and pre/suffix). Hold your horses – this is going to be a long one ;-). You don’t want to know how many hours I spent on this functionality – many points of feedback from the community, and even some pullrequests from some (for all of which I’m very thankful!) has made it into the functionality it is today.
You might remember my post about the Code Analyzers Diagnostic Descriptors when it first came out. I’m very happy with this tool, as it avoids many mistakes, and it enforces some level of clean coding – which is never a bad thing ;-).
Recently, the June update of the AL Language Extension was announced. I was sitting at a swimming pool in Bangkok – so what do you think I did? Exactly:
This was the first major feature that I tried to add. Namely, being able to run an object without having to change and save the launch.json. The easiest way to find the functionality is in the Command Palette. Just search for “>crs:run”, and it will give you all options: