Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

API improvements for common AuditReader methods #18

Open
jonnybbb opened this issue Jul 3, 2014 · 0 comments
Open

API improvements for common AuditReader methods #18

jonnybbb opened this issue Jul 3, 2014 · 0 comments
Labels
status: waiting-for-triage An issue we've not yet triaged

Comments

@jonnybbb
Copy link

jonnybbb commented Jul 3, 2014

I am going to implemented some common reusable methods from the the audit reader (eg: findEntitiesAtRevision). Are those kinds of methods supposed to be included in spring-data-envers or is the prefered way to extend from the existing API within the project?
@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Jan 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
status: waiting-for-triage An issue we've not yet triaged
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jonnybbb @spring-projects-issues