magic-wormhole / magic-wormhole/fowl
setup / teardown code needs more unification
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 163
- Forks
- 14
- Avg merge
- 14h 58m
- Merged PRs (30d)
- 3
Description
There are basically three main "control flow" paths in the code currently: fowl, fowld and fowl --interactive which have some similar but slightly different setup and teardown style of code.
This stuff needs to become more unified. Or something.
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 by comparing the setup and teardown control flow in the fowl, fowld, and fowl --interactive entry points. Identify the differences that need to remain and the behavior that can be unified. Done means the three paths share a clearly defined setup and teardown approach without changing their intended operation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100