Added plugin framework + re-added Slack integration

[jongpie]

Closes #164 and closes #169 by introducing a few new features for the trigger handler classes. This is currently only available in the unlocked package - there are some technical concerns & constraints with bringing this functionality into the managed package.

New Logger plugin framework (beta)

• Added new abstract class LoggerSObjectHandler - the handlers for Log__c, LogEntry__c and LogEntryEvent__e now extend this class
• Added new CMDT object LoggerSObjectHandler__mdt to control the behavior of the handler classes
  • IsEnabled__c - controls if the handler class runs at all
  • SObjectType__c - entity definition-relationship field to indicate which SObject is processed (Log__c, LogEntry__c and LogEntryEvent__e)
• Added new CMDT object LoggerSObjectHandlerPlugin__mdt to define & control any plugins that the handler class should execute
  • SObjectHandler__c - a metadata lookup field, used to relate a plugin to an instance of LoggerSObjectHandler__mdt. This controls when your plugin will execute
  • PluginType__c - the type of plugin to execute. Possible values are 'Apex' and 'Flow'
  • PluginApiName__c - the name of an Apex class or Flow to automatically execute
    • Type == 'Apex' - the name of an Apex class that implements the interface LoggerSObjectPostProcessor
    • Type == 'Flow' - the name of a Flow with the input parameters triggerOperationType, records and oldRecords
• Added new CMDT object LoggerSObjectHandlerPluginParameter__mdt for plugins to store key-value pair configurations

New Slack plugin for Logger (beta)

• Re-added the old Slack integration using the new plugin framework. Formerly a batch job, the new Slack plugin uses a queueable job for asynchronously sending Slack notifications for logs that meet a threshold logging level

[codecov]

Codecov Report

Merging #165 (6fef1d0) into main (5acd00c) will increase coverage by 0.38%.
The diff coverage is 98.85%.

@@            Coverage Diff             @@
##             main     #165      +/-   ##
==========================================
+ Coverage   93.62%   94.01%   +0.38%     
==========================================
  Files          15       17       +2     
  Lines        1915     1971      +56     
==========================================
+ Hits         1793     1853      +60     
+ Misses        122      118       -4     

Impacted Files	Coverage Δ
...in/log-management/classes/LoggerSObjectHandler.cls	97.95% <97.95%> (ø)
...in/log-management/classes/LogEntryEventHandler.cls	98.59% <100.00%> (+0.02%)	⬆️
...er/main/log-management/classes/LogEntryHandler.cls	96.51% <100.00%> (+0.21%)	⬆️
...-logger/main/log-management/classes/LogHandler.cls	99.12% <100.00%> (+0.02%)	⬆️
...management/classes/RelatedLogEntriesController.cls	93.00% <100.00%> (+2.87%)	⬆️
...n-framework/classes/LoggerSObjectHandlerPlugin.cls	100.00% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5acd00c...6fef1d0. Read the comment docs.

[jamessimone]

Nice. Looks like this one is shaping up quickly!

[jongpie]

@jamessimone I made a few small-but-important changes, I'd love to know your thoughts whenever you have a chance:

• I changed LoggerHandler to be a public abstract class that all 3 handler classes now extend (to allow sharing code between the handlers, like a mini trigger framework)
• The interface LoggerHandler.PostProcessor has been removed from LoggerHandler and it's now a standalone global interface called LoggerPostProcessor

[jamessimone]

Two minor comments!

[derroman]

We want to see that! :-D

[jamessimone]

@derroman it’s nearly ready!

[derroman]

need a helping hand? ;-)

[jongpie]

@derroman it's ready! I've merged & released these changes - let us know if you have any feedback!

[derroman]

[cancels every meeting of today] 😂
Great! Looking forward to play around with!