You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be easy to implement but only for Snapshot queries.
JaversRepository stores only snapshots. When you are querying for Changes, first, Snapshot query is executed and then Changes are recalculated as differences between Snapshots pairs.
A list of snapshots would be sufficient for starters. Furthermore the API should be flexible enough to cope with "authorOnly"-Queries. Right now, I don't see a way to query for any changes/snapshots disregarding the entityClass.
Again, any hints if this may be implemented in the near future?
Regarding a pull-request: I may do it myself by modifying the QueryBuilder-class (adding static author-method) and pipe the arguments all through down the way to the repository (similar to commitId-Handling)
Hi @BePe2, we are now in the middle of huge SqlRepository refactoring, so I cant promise you anything,
think about PR. This feature is easy to implement, look at this (merged) PR https://github.com/javers/javers/pull/318/files when commitId filter was added. Author filter can be done in a similar way.