libretro / libretro/libretro-common
TODO: document when to check the system and save paths
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 180
- Forks
- 98
- Avg merge
- 7h 16m
- Merged PRs (30d)
- 1
Description
- clarify that API does not support changing the system or save paths once the core is running
- clarify when the core should check the system and save paths --
retro_load_gameso that the core can fall back on the content path if the frontend has not set system or save path - clarify that the core should fall back on the content path, if indeed that is the standard behavior
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 at the retro_load_game entry point and review the surrounding libretro API documentation and path-handling guidance. Determine where the documentation should state that paths cannot change after the core starts, when paths are checked, and whether fallback to the content path is standard. Done means all three behaviors are documented consistently.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100