v4.13.0 - Spring '24 Release

[jongpie]

Managed Package Release - v4.13.0

This release is for both the unlocked package (as always), as well as the managed package! You can see everything that's changed between v4.12.0 and v4.13.0 by reviewing:

• The v4.13.0 milestone to see all of the issues & pull requests that are included in the this release.
• The diff between v4.12.0 and v4.13.0 to see all of the code & metadata changes that have been committed since the last managed package release.

✅ For orgs that are upgrading to this version of the managed package: this release now provides the managed package with the ability to log in lightning components! 🥳🎉 This functionality has been available in the unlocked package since v4.6.4, but has been unavailable in the managed package... until now!

• Using the Nebula namespace, you can import the included logger LWC into your own LWC and log what's happening in the frontend:

  import { createLogger } from 'Nebula/logger';
  
  export default class LoggerLWCDemo extends LightningElement {
    logger;
    
    async connectedCallback() {
      this.logger = await createLogger();
      this.logger.info('Hello, world');
      this.logger.saveLog();
    }
  }

Thanks so much to @jamessimone for all of the help working on the logger LWC this release! 🥳

Core Unlocked Package Changes - v4.13.0

Spring '24 Release Upgrade

• Bumped all metadata to API v60.0 (Spring '24 release)
• Optimization & cleanup - Switched to using the new standard class System.UUID, instead of my custom UUID class. The new system class is soooo much faster.

logger LWC Bugfixes & Improvements + Enabled logger LWC in the Managed Package

• Worked with @jamessimone to fix Logs are not generating each time for Lwc and Aura #615 by optimizing how logger LWC loads user settings async (as well as several other optimizations throughout the LWC). The component should now log & save entries correctly, but developers need to either use await or chain .then() when calling createLogger().

  Here is an example of using await

  import { createLogger } from 'c/logger';
  
  export default class LoggerLWCDemo extends LightningElement {
    logger;
    
    async connectedCallback() {
      this.logger = await createLogger();
      this.logger.info('Hello, world');
      this.logger.saveLog();
    }
  }

  This example uses .then() in connectedCallback() (instead of await). Additionally, this example shows renderedCallback() using a truthy check on logger to ensure it's been initialized before trying to use it.

  import { createLogger } from 'c/logger';
  
  export default class LoggerLWCDemo extends LightningElement {
    logger;
    
    connectedCallback() {
      createLogger().then(async logger => {
        this.logger = logger;
        this.logger.info('Hello, world');
        await this.logger.saveLog();
      });
    }
  
   // and maybe even ...
    renderedCallback() {
      // this.logger may not be defined for initial renderings
      // you can either use a guard clause:
      if (this.logger) {
        this.logger.info('Some info about a re-rendering');
      }
      // or safe navigation:
      this.logger?.info('Some info about a re-rendering');
    }
  }

• Fixed How do I use the lwc logger with the Nebula namespace? #533 by updating logger.js-meta.xml so the isExposed node is set to true - this change makes the logger LWC available to use in the managed package for JavaScript logging. You can import it using the Nebula namespace.

Bugfixes

• Fixed an issue in LoggerDataStore where not all string fields were truncated for platform events. This functionality was originally introduced in v4.12.6
  • Also optimized how the code looks for string fields to truncate to reduce some unnecessary looping
• Fixed an issue with the optional Status API integration (used to retrieve additional details about the current org's Salesforce instance) - Updated LogManagementDataSelector to always return null in getCachedRecentLogWithApiReleaseDetails() when LoggerParameter.CALL_STATUS_API is false
  • In previous versions, this method would still query the Log__c object, even if the optional Status API integration was disabled. But when the callout is disabled, this query will never be able to find a match, because the relevant fields haven't been populated by the callout. And in orgs with large data volume (LDV) of logging data, the condition ApiReleaseNumber__c != NULL is a very expensive query operation.
  • This change will now skip the unnecessary (and sometimes expensive) SOQL query when the integration is disabled
• Fixed RelatedLogEntriesController_Tests sometimes throws an uncatchable UnexpectedException when using SOSL #624 by commenting out a flappy test in RelatedLogEntriesController_Tests that's been frequently failing due to ongoing platform issues with SOSL. It throws an uncatchable UnexpectedException due to Salesforce platform issues, resulting in (apparently) several pipelines failures for multiple companies that use Nebula Logger in their CI/CD jobs 😢
  • "Fixed" ¯\(ツ)/¯ - The functionality being tested has not changed in a few years, so commenting-out the test for now seems safe, and should prevent unnecessary pipeline failures for anyone that's been impacted by this problem.

Installation Info

Core Unlocked Package - no namespace

Full Changelog: v4.12.9...v4.13.0

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

Core Managed Package - Nebula namespace

Full Changelog: v4.12.0...v4.13.0

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

---

This discussion was created from the release v4.13.0 - Spring '24 Release.