![]() ![]() ![]() Using this approach, Graph Engine consumes the entire code source simultaneously, and assimilates this information to produce a better understanding of what’s happening in the code. As a quick refresher, Graph Engine typically scans code using a path-based approach using something we call “data flow analysis” (DFA). We added these new rules to Salesforce Graph Engine. You can use these two rules to remove unused code and make your code smaller, more efficient, and therefore more performant (but more on that later). It complements another rule that we introduced in version 3.8, UnusedMethodRule that detects unused methods. Specifically, it detects unused interfaces and abstract classes. With Code Analyzer version 3.9 we’re introducing a new performance rule, UnimplementedTypeRule, that detects whether you have unused Apex code in your solution. So, sit back, relax, and get ready to accelerate your code! New performance rules in version 3.9 Today, we’ll share how, with our version 3.9 release, we’re evolving Graph Engine with new rules to help you boost your code’s performance. ![]() In particular, we did a deep-dive on Salesforce Graph Engine, which uses data flow analysis to detect advanced security vulnerabilities in code. Back in October 2022, we shared exciting news about the version 3.x release of Salesforce Code Analyzer, our free code scanner that brings together multiple open-source code analysis engines under a unified Salesforce CLI experience. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |