Custom Field Mappings Support for Lightning Components

[jongpie]

Core Unlocked Package Changes

Resolved #718 by adding the ability to set custom fields on a log entry in JavaScript (lightning components), using a new function setField() in logEntryBuilder.js. This is equivalent to the Apex method overloads setField() in LogEntryEventBuilder.cls that were introduced in release v4.13.14.

• To use the new setField() function, pass an object as the function's single parameter. The object should contain the custom fields on LogEntryEvent__e that you want to set, along with their corresponding values. For example: { SomeField__c": "some value", "AnotherField__c": "another value" }

  import { createLogger } from "c/logger";
  
  export default class LoggerCustomFieldDemo extends LightningElement {
  logger;
  
  async connectedCallback() {
    this.logger = await createLogger();
  
    this.logger.info("Hello, world! This log entry has 2 custom fields set.")
      .setField({
        SomeCustomTextField__c: "some text value",
        SomeCustomNumberField__c: 123,
      });
  
    this.logger.debug("Hello again, world! This log entry has 1 other custom field set.")
      .setField({
        AnotherCustomTextField__c: "another text value",
      });
  
    this.logger.saveLog();
  }
  }

[!NOTE]
The code above only highlights the new functionality that is now available when logging in lightning components. For more info on how to fully set up custom field mappings, see this section in README.md

Recipes Metadata Changes

• Updated the demo lighting components in the recipes metadata folder to set a custom field on LogEntry__c. This just makes it quick & easy to verify that the functionality works for lightning components.

[codecov[bot]]

Codecov Report

Attention: Patch coverage is 96.55172% with 1 line in your changes missing coverage. Please review.

Project coverage is 93.16%. Comparing base (4fe4c36) to head (76a97cd).

Files	Patch %	Lines
...e/main/logger-engine/lwc/logger/logEntryBuilder.js	92.30%	1 Missing :warning:

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #749 +/- ## ======================================= Coverage 93.16% 93.16% ======================================= Files 67 67 Lines 6935 6950 +15 Branches 198 199 +1 ======================================= + Hits 6461 6475 +14 - Misses 446 447 +1 Partials 28 28 ``` | [Flag](https://app.codecov.io/gh/jongpie/NebulaLogger/pull/749/flags?src=pr&el=flags&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=Jonathan+Gillespie) | Coverage Δ | | |---|---|---| | [Apex](https://app.codecov.io/gh/jongpie/NebulaLogger/pull/749/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=Jonathan+Gillespie) | `95.46% <100.00%> (+0.01%)` | :arrow_up: | | [LWC](https://app.codecov.io/gh/jongpie/NebulaLogger/pull/749/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=Jonathan+Gillespie) | `83.26% <92.30%> (-0.08%)` | :arrow_down: | Flags with carried forward coverage won't be shown. [Click here](https://docs.codecov.io/docs/carryforward-flags?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=Jonathan+Gillespie#carryforward-flags-in-the-pull-request-comment) to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.