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:
It turned out I downloaded the wrong one :-). I needed to download from the daily build “bcinsider.azurecr.io/bcsandbox-master”.
Anyway, when playing with it, I noticed there was an update on the analyzers as well – so it seemed interesting to update my previous blog in the descriptors, and let’s see what we have now. There are new descriptors, fixed descriptors, and even a whole new CodeCop, the UICop!
This is the one that is use for extensions that will be used on AppSource – and on this one, nothing has changed.
The CodeCop is the one you should always align with. It’s the one that basically has general descriptors – which are always interesting. And in this one, we have two more “rules” we have to take into account – I put them in yellow. Both are quite logical, but now at least you have descriptors/rules/analysers that prevent you from doing things like that ;-).
When you are doing customer development for a customer on the Business Central cloud, you are actually doing a “Per Tenant Customization”. The PerTenantExtensionsCop contains the rules to comply with. Nothing new, but there are a few fixes, as in the previous version, there was a hardcoded range of 50000..50099 in the first two descriptors.. .
This is the new one! A whole new analyzer for you to use to be able to comply with the Web Client.
Now you know!