Description
In JaVers all objects and their properties are audited by default. There are various ways to ignore some of them.
This approach becomes hard when a user wants to audit only a small fraction of his data.
Opposite or mixed approach can be developed to give more control over type mapping process to JaVers user. Since we don't want to add more annotations to JaVers, the solution would be based on filters.
There are two API changes that we need:
-
List of includedProperties added to
ClientClassDefinition(see https://github.com/javers/javers/pull/615/files#diff-582e4833c9094529597d16ce39589eb6) -
Possibility to register a
ClientsClassDefinitionFilter. By implementing this filter, a user would be able to, for example: changeEntityDefinitionintoIgnoredTypeDefinition, or addincludedPropertieslist to raw EntityDefinition produced by JaVers'ClassScanner.
/** Hook here to change a ClientsClassDefinition produced by ClassScanner */
interface ClientsClassDefinitionFilter {
ClientsClassDefinition applyFilter(ClientsClassDefinition source);
}
Activity
#616 first passing test
#616: Added DifInclude annotation and updated code to take that into …
#616: fixed issue with conversion from String[] to Set<String>. Added…
bartoszwalacik commentedon Feb 6, 2018
property-level
@DiffIndludereleased in 3.8.0