@PhilW_SF Maybe the implementation is in the namespace, I just don't want to expose the abstraction. I would probably use an interface instead then, but struck me as rather prescriptive all the same.
🎉 v1.16.0 of Apex Debug Log Analyzer is out with find in the analysis, more ways to open the analysis, a new docs site, a faster Call Tree, faster extension startup and more
https://t.co/XR0TDYUIHm
here's a whats new thread 🧵
@SalesforceDevs#SalesforceDevs#Salesforce
1/10 ENTERING_MANAGED_PKG Apex debug log events can make it impossible for the Apex debug log analyzer to determine which managed package DML and SOQL happened in. Vote to improve the handling.
https://t.co/rWFrFPa4SV
Other useful ideas in thread
@salesforcedevs#apexdebuglog
@FishOfPrey If that is our only resolution then I don't think this is usable for ISVs, we bump into prod orgs where it has been disabled via Case and it would create too many issues within the dev teams.
Anyone know what is going on with ApexTypeImplementor and invalid classes. The doc, https://t.co/iXiNIInpKR, explicitly states they will be returned, but hit an issue with them being missing until isValid=true.
@FishOfPrey@FishOfPrey Looking like we could do with help to get this Case resolved. If I am understanding, if the class has never been compiled, ApexTypeImplementor won't see it. Not sure what we are supposed to do to make sure it is compiled, not something we usually worry about.
The release of @pmd_analyzer 7 this week is a special moment for @SalesforceDevs. 8 years after I ported it to Salesforce, we finally have: a fully open-source Apex parser (🙏@nawforce et al.), Salesforce as contributor(🙏@johnbelo et al.) and a new logo😅 https://t.co/q9liHlE4iA
@FishOfPrey Will get a Case raised, but context was interface and classes in same 1GP managed package, failure was seen on a sandbox during release testing. We have been able to hardcode a workaround for now, but intent of design is broken.
Great news: @pmd_analyzer is around the corner and will replace the recent closed-source parser with open-sourced ones by @google and @nawforce. But that is not enough: It looks like Salesforce plans to directly contribute and help maintain this parser. 😉
https://t.co/X93ss9QEYh
@rsoesemann@ch_sz_knapp@codefriar@johnbelo Null Coalescing is in works at moment, https://t.co/O0PvsrVXUS. Note: we have moved the parser location to align with other work but it's the continuation of https://t.co/8oaOHAepOd
@jodiem I have raised this exact thing with support.
You get one entry event per constructor/ method call etc that occurs in that package.
I raised an idea to simplify the clutter by adding an exit event and only logging entry on the first package entry
https://t.co/rWFrFPa4SV