-
-
Notifications
You must be signed in to change notification settings - Fork 234
The managed package should never attempt to call System.debug() #889
Copy link
Copy link
Open
Labels
Layer: Logger EngineItems related to the core logging engineItems related to the core logging enginePackage Type: Managed PackageIssues and enhancements that specifically apply to the managed packageIssues and enhancements that specifically apply to the managed packageType: EnhancementNew feature or requestNew feature or request
Milestone
Metadata
Metadata
Assignees
Labels
Layer: Logger EngineItems related to the core logging engineItems related to the core logging enginePackage Type: Managed PackageIssues and enhancements that specifically apply to the managed packageIssues and enhancements that specifically apply to the managed packageType: EnhancementNew feature or requestNew feature or request
In the current version of
LogEntryEventBuilder, it only checks the fieldLoggerSettings__c.IsApexSystemDebugLoggingEnabled__cto determine if it should callSystem.debug(). But for the managed package (any managed package), callingSystem.debug()won't work (Salesforce hides the managed package's debug lines from the customer org). This results in a performance tax, with no benefit to the managed package.The builder class's code needs to be updated to also detect if the code is running in a namespace/managed package - if so, don't call
System.debug().