coffee-tools / coffee-tools/coffee
Plugin Bug Reporting in Plugins
- Dominant language
- Rust
- Stars
- 11
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
### Description:
We currently lack a simple way for users to report bugs in plugins.
### Suggested Implementation:
1. **Manifest Update:** Add a new field in the plugin manifest for the developer's email address for bug reporting.
2. **User Command:** Introduce a new command (e.g., `coffee report `) for users to report plugin issues briefly.
### Similar Cases in Other Projects:
**Brew:**
- In Brew, the `brew info ` command provides various details about a package, including the developer's email address. This is not explicitly designed for bug reporting but this kind of information could be used as well to report issues.
Contributor guide
Research direction
Start by locating the plugin manifest handling and the CLI command entry point. Define how a developer email is stored and displayed, how the plugin and issue text are validated, and what successful reporting should do; consider the existing `brew info ` behavior as a reference.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100