Path config with `~` on macOS seems to not work
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- react-native, typescript
- Domain
- databases, mobile-dev
Research direction
Start with the reproduction's src/Storage.js and confirm the behavior using the path '~/.test' on macOS. Then trace the path configuration and constructor validation in the relevant MMKV entry points. Done means the reported path behavior and the config without an id have clearly defined, tested behavior.
Written by the indexing model from the issue text.
Description
Lately, I have switched from AsyncStorage to MMKV in on of the macOS test projects, and I would like to utilize the path config, but it looks like that, when path includes tilde (~) file is not saved. Not sure if this is intended to work, but I have decided to report this anyway, so feel free to close this one or convert to feature request.
Other thing which was a bit unexpected is that you cannot use the constructor with config object, but without the id field (no fallback to default?), so for example when path and encryption field are the only present, this leads to error about missing ID.
Repro
- Clone: https://github.com/Simek/react-native-macos-reminders
- Edit: https://github.com/Simek/react-native-macos-reminders/blob/master/src/Storage.js
- Add:
path: '~/.test'config option
- Dominant language
- TypeScript
- Stars
- 8.5k
- Forks
- 347
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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.
More from margelo/react-native-mmkv
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
margelo/react-native-mmkv#1099 ·
-
deleteMMKV() crashes on next foreground: AppState listener still calls checkContentChanged() on the destroyed instancePossibly taken @qutrek claimed this 34 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 48/100
margelo/react-native-mmkv#1082 · 5 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
margelo/react-native-mmkv#100 · 48 comments · 11 reactions ·
-
Windows supportMay be free again A pull request for this issue was closed without being merged. Openenhancement help wanted
Difficulty 4/5 3-5 days Newbie friendliness 25/100
margelo/react-native-mmkv#12 · 9 comments · 6 reactions ·
All issues in margelo/react-native-mmkv
Similar issues
-
cloudflare-cache-binding: `unstorage://` keys are rejected by the Cache API, cache never storesOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 2 days
-
reproduced
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
anomalyco/opencode#62052 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
strapi/design-system#2084 ·
Maintainers usually reply within 3 days
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day