stacklok / stacklok/toolhive-studio
[Bug] Command arguments is pretty confusing to users
Open
Nobody has claimed this yet.
Bug
- Dominant language
- TypeScript
- Stars
- 167
- Forks
- 24
- Avg merge
- 11h 32m
- Merged PRs (30d)
- 91
Description
Bug Description
I think this is pretty confusing to users (Alejandro asked what he needs to put in there and I hadn't a fucking clue).
Two suggestions...
- if it's rarely required, we make it less prominent (say under a collapsed panel called 'Advanced options'
- that we do a better job explaining it ('Space separated arguments for the command' means literally nothing to me)
Steps to Reproduce
No response
Expected Behavior
No response
Actual Behavior
No response
Priority
Medium
Environment
No response
Additional Context
No response
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 by locating the UI that displays the command-arguments field shown in the issue screenshot and review its current label and surrounding controls. Confirm with maintainers whether the intended outcome is an Advanced options collapse, clearer explanatory text, or both; done means users can understand when and what to enter.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100