There is something that has never been a thing in code review that is:splitti...
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 157
- PR merge metrics
- No merged PRs in 30d
Description
There is something that has never been a thing in code review that is:splitting the test code from the production code. I might not care about the test or only want to review tests to know if the use cases are covered.
Another interesting feature would be to be able to pop-out the right panel into a separate window to have it on another screen.
| Field | Value |
|---|---|
| App version | 1.1.19 |
| OS | macOS 26.6.2 |
| Theme | Vaporizer Turquoise |
| Path | /chat |
| Tenure | Week 6 |
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 at the /chat experience and identify the code-review interface and its right panel. Define the behavior for separating test code from production code and for popping the right panel into another window; done means both interactions work reliably in the desktop app.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100