microsoft / microsoft/react-native-windows
Allow storage-backed Blob content
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
Current implementation of Microsoft::React::IBlobPersistor stores Blob payloads in memory using a std::unordered_map<uint8_t>.
See https://github.com/microsoft/react-native-windows/blob/react-native-windows_v0.70.6/vnext/Shared/Modules/BlobModule.cpp#L245
This blocks apps from performing when handling multiple sufficiently large blobs, for the will stay in memory even if not currently used.
Design and implement a device storage implementation of IBlobPersistor that works on both UWP apps and Desktops (Win32) clients (don't assume the eventual blob persistor will be able to rely on Windows.Storage as an app container).
Contributor 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.
Research direction
Start with Microsoft::React::IBlobPersistor and BlobModule.cpp around line 245, then consider the UWP and Win32 client constraints described in the issue. Done means a device-storage implementation supports both targets without assuming Windows.Storage is available as an app container, while replacing the current in-memory blob persistence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, react-native
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100