Added support for custom field mappings

[jongpie]

Resolves #655 by adding support for defining, setting, and mapping custom fields within Nebula Logger's data model. This is helpful in orgs that want to extend Nebula Logger's included data model by creating their own org/project-specific fields.

Adding custom fields to the platform event LogEntryEvent__e

For orgs that only use LogEntryEvent__e (and don't leverage the custom objects), they can now...

• Create their own custom fields on LogEntryEvent__e. Any data type supported by platform events can be used.

  • In this example, a custom text field called SomeCustomField__c has been added:

    

• Populate their own custom fields in Apex by calling the instance method overloads LogEntryEventBuilder.setField(Schema.SObjectField field, Object fieldValue) or setField(Map<Schema.SObjectField, Object> fieldToValue).

  • For now, this functionality will only be available in Apex. Long-term, Flow & Lightning Components might also benefit from having equivalent functionality, but that will be handled separately.
  • Example: Logger.info('hello, world').setField(LogEntryEvent__e.SomeCustomField__c, 'some value');

Adding custom fields to the custom objects Log__c, LogEntry__c, and LoggerScenario__c

For orgs that want to store the data in one of Nebula Logger's custom objects, they can follow the above steps, and also...

• Create their own custom fields on one of Nebula Logger's custom objects - right now, only Log__c, LogEntry__c, and LoggerScenario__c are supported.

  • In this example, a custom text field also called SomeCustomField__c has been added to Log__c object - this will be used to store the value of the field LogEntryEvent__e.SomeCustomField__c:

    

• Create a record in the new CMDT LoggerFieldMapping__mdt to map the LogEntryEvent__e custom field to the custom object's custom field, shown below. Nebula Logger will automatically populate the custom object's target field with the value of the source LogEntryEvent__e field.

  • In this example, a custom text field called SomeCustomField__c has been added to both LogEntryEvent__e and Log__c.

    

[codecov]

Codecov Report

Attention: Patch coverage is 84.94624% with 14 lines in your changes missing coverage. Please review.

Project coverage is 95.51%. Comparing base (48ea5fe) to head (0ce0424).

Files	Patch %	Lines
...e/main/configuration/classes/LoggerFieldMapper.cls	84.12%	10 Missing ⚠️
...r/core/main/configuration/classes/LoggerPlugin.cls	66.66%	2 Missing ⚠️
...ain/logger-engine/classes/LogEntryEventBuilder.cls	88.23%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #664      +/-   ##
==========================================
- Coverage   95.66%   95.51%   -0.15%     
==========================================
  Files          50       51       +1     
  Lines        5604     5687      +83     
==========================================
+ Hits         5361     5432      +71     
- Misses        243      255      +12     

Flag	Coverage Δ
Apex	95.51% <84.94%> (-0.15%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.