Skip to content

Whitelisting audited classes & properties #616

Closed

Description

@bartoszwalacik

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:

/** Hook here to change a ClientsClassDefinition produced by ClassScanner */
interface ClientsClassDefinitionFilter {
    ClientsClassDefinition applyFilter(ClientsClassDefinition source);
}

Activity

  1. added a commit that references this issue on Jan 14, 2018
  2. added 2 commits that reference this issue on Jan 23, 2018
  3. bartoszwalacik commented on Feb 6, 2018

    @bartoszwalacik
    MemberAuthor

    property-level @DiffIndlude released in 3.8.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions