tmux-python / tmux-python/libtmux
Configuration object / knob
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 127
- Avg merge
- 2h 13m
- Merged PRs (30d)
- 1
Description
Their should be a configuration object
Default / regular usage should never need to use it
But for any implied defaults, their should always be a way to override them. These should be tested and documented, with examples
The configurations should also allow overriding at the object level, in an overlay / patching style. Where the uppermost configuration knows are inherited but can be overridden at a lower level
Similar to pytest fixture overrides, except dealing with a configuration object specifically, rather than tests
Though these configuration knobs would make various types of testing easier
And also, the "override" at the object level would be perfect for context managers
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
No files, tests, or entry points are named. Start by mapping how libtmux currently defines defaults and object state, then clarify the configuration API, inheritance and override rules, testing needs, documentation examples, and the criteria for considering the feature complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100