max-mapper / max-mapper/dat-core
opt in for 'get on put'
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 42
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
default should be that puts override data, but you should be able to say 'only put if the key doesnt exist'
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
No file or test is named; start by locating the JavaScript implementation of put/get-on-put behavior and any existing write tests. Trace how a put handles an existing key, then verify that default puts still override while the opt-in preserves an existing value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend, data
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100