New Release v4.8.0 - Summer '22 Release

[jongpie]

This (slightly late) release is for both the unlocked package (as always), as well as the managed package! If you use the managed package & are upgrading, you can review the v4.8.0 milestone to see all of the issues & pull requests that are included in the this release. ⚠️ For orgs that are upgrading to this version of the managed package: it's recommended that you review LoggerSettings__c and LoggerParameter__mdt records in your org, since some configuration options have changed.

New Features

• Closed Add a way to bypass/ignore additional Apex classes when calculating each entry's origin details #335 by adding new method Logger.ignoreOrigin(Type apexType) - this allows plugins/external code to specify Apex classes to ignore when parsing each log entry's stack trace/origin (requested by @jamessimone for apex-rollup's nebula logger plugin and requested by @TKGC in Setting Origin__c on LogEntry__c #330)
• Bumped all metadata to API v55.0 (Summer '22 release)

Bugfixes

• Fixed Dead Link in Readme #331 (reported by @justin-lyon) by correcting some links in README for the docs site
• Fixed Custom Object LoggerSObjectHandlerParameter__mdt from managed package not present for recipes #339 (reported by @hernandezjesus) by cleaning up the Admin.profile that's currently included with the recipes metadata - the Admin.profile will eventually be replaced with a new permission set, but for now, this should make the metadata deployable
• Fixed Logger.info(String message, List<SObject> records) throws index out of bounds error #340 (reported by @EoghanMcMullen) by adding some extra checks for empty lists in LogEntryEventBuilder's methods stripInnaccessible() and getJson()
• Fixed a null object exception that could occur in LogMessage when the message template is null (something I noticed when discussing Contructor of LogMessage with Database.SaveResult as param #342)
• Fixed Logger fails to save Log Entries due to duplicate UUIDs when run from Scheduled Flow #345 (reported by @eclarke12) by switching to using upserts (instead of inserts) for LogEntry__c and LogEntryTag__c records
• Fixed LWC Component Name doesn't populate when creating a log from LWC #346 (reported by @EllieAtWHL) by updating test stack traces for Aura & LWC to reflect the latest content + updating the logic used for parsing the component's stack trace
• Fixed 2 Test Cases in LogEntryEventBuilder_Tests class is failing #352 (reported by @adityavgpl) by updating a few failing tests to not run when the code is using a namespace prefix - due to platform limitations with stack traces, some of the tests simply will not work when running in the managed package
• Fixed an unreported issue where anonymous mode (controlled via LoggerSettings__c.IsAnonymousModeEnabled__c) would still assign the log to the logging user, resulting in the Log__c not being fully anonymous. Now, if the logging user has anonymous enabled, then the Log__c will be assigned to the user executing the class LogEntryEventHandler - typically, this is the Automated Process users, but orgs have the ability to specify a different user

Thanks to everyone that helped with this release!

---

This discussion was created from the release v4.8.0 - Summer '22 Release .