LogBatchPurger - hard delete vs delete

[szymon-lechowicz]

Hi!

Our customer currently plans to include Nebula logger managed package in already existing Logging logic.

I have a question because currently our custom Logging records are deleted, not hard deleted like it is in Your code. However Nebula Custom Settings displays the possibility to change Log Purge Action with provided help text that this value is passed into Log__c.LogPurgeAction__c but I cannot see any check on that field in batch job. Is this field obsolete and not really in use as only one picklist value is available? Or the field was firstly created and you plan to extend the logic in the future?
I can propose the idea that both delete and hard-delete can be possible to choose for Your batch job. It requires then to rebuild your class locally which is another effort from our side.

Package Edition
Managed Package

Package version
4.16