[Feature Request] Add option to save runtime log by content directory
Open
Nobody has claimed this yet.
feature request
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Current options allow the runtime logs to be saved in aggregate and/or core directory. Requesting the option be added to save the logs by content directory, which would align the runtime log options with the options available for saves and save states.
Thank you!
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 by locating the existing runtime-log path handling for aggregate and core directories, then compare it with the directory options used for saves and save states. Done means a content-directory option is available and runtime logs are written under the corresponding content directory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100