N°6275 - Propose CaseLog extensibility API to manage history #493
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why?
ormCaseLog tend to become huge sometimes (seen in iTop SaaS infrastructure). it could be nice to implement some shrinking logic.
There is also a remaining bug regarding broken indexes:
Current PR aims at proposing an extension API to manipulate ormCaseLog objects (while calling constructor/AddLogEntry* methods). With such an API we could for example propose some repairment algorithm apart from any iTop release.
** Configuration **
Once you have written your own classes that implement iOrmCaseLogExtension interface, you have also to configure which one will be enabled via iTop following configuration variable: ormcaselog_extension_classes
This is the sorted list of enabled extension.
Example of proposed configuration (config-itop.php):