Roopa

Software nerd, musician

[Roopa @rmohan_sfdc]

Join @johnbelo and me today at 11:30am #TDX23 to find out how you can get the best value out of Code Analyzer. We have a large breakout theater this time!

[Mohith Shrivastava @msrivastav13]

Really looking forward to this tomorrow!

You can start your questions right now too and I will start queuing it to our experts!!!

[Salesforce Developers @SalesforceDevs]

Join us Feb 22 for our next #SalesforceDevsAMA about Salesforce Code Analyzer! Join @msrivastav13, @johnbelo and @rmohan_sfdc as they answer your questions LIVE. Learn more and add to calendar: ➡️https://t.co/DCPrJwSL9V

[Roopa @rmohan_sfdc]

@badoitmenthe @SalesforceDevs Please do check out UnimplementedTypeRule as well: https://t.co/q6d8oRDJIS
In general, you can reach out to us directly through https://t.co/EAi5nfXQoi with discussion topics, bug reports and feature requests. Thank you!

[Roopa @rmohan_sfdc]

@badoitmenthe @SalesforceDevs Thanks much for trying out the new rule! We're working on iteratively detecting more categories of unused methods.
https://t.co/mBf9dUHhxK This documentation talks about the cases we cover. We'll update it every release as we handle more scenarios.

[Doug Ayers @douglascayers]

The #Spring23 release is here and what better time than to do some Spring cleaning and remove unused Apex code from your #Salesforce orgs? 🌼

https://t.co/88zwIywxI1

[Robert Sösemann @rsoesemann]

And thanks @rmohan_sfdc for all your work on the scanner. And for explaining it so well.

[Roopa @rmohan_sfdc]

Great fun geeking out with the fantastic @joshbirk! We spoke about Code Analyzer, data flow analysis, guilty refactors, and everything in between :D

[Josh Birk (not a parody) @joshbirk]

Apologies to the amazing @rmohan_sfdc that the browser player didn't load correctly. Clerical error in the form of me. But if you listen to the show in a tab, it's up and running and just a great talk about code
#sfdevpod
https://t.co/6YnTwJOxaY

[Salesforce Developers @SalesforceDevs]

We’re evolving Salesforce Graph Engine with new rules to boost your code’s performance! Check out the latest changes in Code Analyzer version 3.9: ⬇️ https://t.co/kPx0Ln7JIW

[Salesforce Developers @SalesforceDevs]

Salesforce Code Analyzer combines the power of many static analyzers to produce something truly awesome. 👀 Hear more about how it works and how to use it from @rmohan_sfdc in today’s episode of the #SalesforceDevs podcast: https://t.co/ASYdO8iuIo

[Roopa @rmohan_sfdc]

@badoitmenthe @SalesforceDevs Could you try again? We've fixed the issue.

[Roopa @rmohan_sfdc]

@joshbirk Such fun talking to you! You make it soo easy :) Thanks for the wonderful opportunity!

[Roopa @rmohan_sfdc]

@rsoesemann @pmd_analyzer Absolutely, hoping for the same!
We don't have a decisive timeline on newer rules - our focus has been on strengthening the existing CRUD/FLS detection rule and SFCA 3.x in general to make it the default version by September 2022.

[Robert Sösemann @rsoesemann]

Here is the recording of the mentioned #TDX22 session. Thank you so much @rmohan_sfdc and team for your great work and collaboration in the past. And for the kind shoutout to @pmd_analyzer. I still hope we can bring some of this into #PMD. https://t.co/AFU2OBzXQs

[Robert Sösemann @rsoesemann]

A hidden gem silently released on #TDX22: Salesforce Graph Engine - a Data Flow analysis add-on for the Salesforce Code Analyser. It's overcoming the one-file-only restriction of @pmd_analyzer and bringing OSS-tooling on par with the commercial analyzers. https://t.co/qtpHaSaMsH

[Roopa @rmohan_sfdc]

@rsoesemann @pmd_analyzer So happy to see your tweet today morning :) thanks for trying out the new engine and telling the world about it! As always, we appreciate your feedback and inputs.

[Roopa @rmohan_sfdc]

Excited to see you all tomorrow at #TDX22!
@appexchange Join me to know about the newest capabilities of the Salesforce Code Analyzer to help you write cleaner and more secure code.

https://t.co/bk49iiDiLM

[Roopa @rmohan_sfdc]

@FishOfPrey @msrivastav13 @SalesforceDevs @FishOfPrey target parameter can take a comma separated list of target paths that could be a pattern, file or directory

[Roopa @rmohan_sfdc]

Try out the open-sourced Salesforce CLI Scanner that my team and I are actively developing. Send us your feedback through GitHub and help us shape the product!

[Salesforce Developers @SalesforceDevs]

Have you used the Salesforce CLI Scanner yet? It's an intuitive open-source tool that can scan your code to identify common coding issues and possible vulnerabilities. Check it out: https://t.co/prhVKMotkO

[Roopa @rmohan_sfdc]

@rsoesemann @DavidBrowaeys @pmd_analyzer @SalesforceDevs @salesforce Have you tried using the run command with —format junit parameter? That should create failing violations. Will respond on the issue as well. Thanks for trying the plugin and providing your helpful feedback :)