DapperLib / DapperLib/Dapper.Contrib
Snapshotter allow public access to original clone?
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 293
- Forks
- 109
- PR merge metrics
- No merged PRs in 30d
Description
Hi, I'm using Snapshotter to detect changes and trigger updates.
I also use it to trigger events depending on which field changed and the value before and after.
I obviously have the value after change because it's the current value of the object being tracked, but I have no way of accessing the old value because the cloned object is private.
Could we make this public? Or Is there another intended way of using it?
It's a waste of ressources of force to clone the object outside AND inside the snapshotter.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating Snapshotter and the private cloned object, then inspect its public API and any related tests. Determine how the original snapshot can be exposed or accessed without requiring a second clone; done means callers can read pre-change values while existing change detection continues to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100