Use Case Descriptions
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 12.4k
- Forks
- 510
- PR merge metrics
- No merged PRs in 30d
Description
We should gather use-cases from people around the community to help guide further Toxiproxy development. This will help us find out what people use, what they don't use, and what the major sources of frustration (or happiness is).
@xthexder
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
No files, tests, or entry points are named. Start by reviewing the issue body and determine how community use cases, usage patterns, and sources of frustration or satisfaction should be gathered and recorded; done means producing a useful collection that can guide future Toxiproxy development.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100