v4.12.7 - Bugfix for Broken LWC Stack Trace Parsing

[jongpie]

Core Unlocked Package Changes

Fixed Stack Trace Parsing for Lightning Web Components (LWCs)

• Fixed LWC Component Name doesn't populate when creating a log from LWC #346 again (previously fixed in v4.8.0) and partially fixed Logs are not generating each time for Lwc and Aura #615 by updating ComponentLogger.cls so it handles recent-ish changes to the format of stack traces in LWCs.
  • Previously, this bug would have resulted in fields like LogEntry__c.OriginLocation__c and LogEntry__c.StackTrace__c being incorrectly set to null for log entries generated via LWCs using the logger LWC.
  • Also updated ComponentLogger_Tests to validate that the logic in ComponentLogger handles different variations of LWC stack traces, so hopefully there aren't future regression issues with this functionality

Installation Info

Core Unlocked Package - no namespace

Full Changelog: v4.12.6...v4.12.7

• SF CLI: sf package install --wait 20 --security-type AdminsOnly --package 04t5Y000001Mk21QAC
• SFDX CLI: sfdx force:package:install --wait 20 --securitytype AdminsOnly --package 04t5Y000001Mk21QAC
• Sandbox: https://test.salesforce.com/packaging/installPackage.apexp?p0=04t5Y000001Mk21QAC
• Production: https://login.salesforce.com/packaging/installPackage.apexp?p0=04t5Y000001Mk21QAC

---

This discussion was created from the release Bugfix for Broken LWC Stack Trace Parsing .