emscripten-core/emscripten

Doc request: How does emscripten MEMFS persist link information in IDBFS?

Open

#15,789 opened on Dec 15, 2021

View on GitHub
 (12 comments) (0 reactions) (0 assignees)C++ (27,361 stars) (3,519 forks)batch import
docsgood first bughelp wanted

Description

Please include the following in your bug report:

I asked this question on SO and was suggested to ask for an update to the docs. https://stackoverflow.com/questions/70368027/how-does-emscripten-memfs-persist-link-information-in-idbfs

Contributor guide

Tech stack
ccppwasmjavascript
Domain
documentation
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic understanding of Emscripten's virtual filesystemFamiliarity with MEMFS and IDBFS
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Review the Stack Overflow question linked in the issue for the exact query. Examine the current Emscripten documentation on filesystem persistence, particularly the MEMFS and IDBFS sections. Look through the 12 comments to see if any maintainers have provided partial explanations or suggested approaches. The goal is to add a clear explanation of how link information is stored by MEMFS and persisted to IDBFS, including any relevant code paths in the source.
Doc request: How does emscripten MEMFS persist link information in IDBFS? · emscripten-core/emscripten#15789 | Good First Issue