More Inconsistencies between `local()` and `local_resource()`
Open
Nobody has claimed this yet.
bug
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Description
The functions local() and local_resource() are very closely related, but have some inconsistencies (see #3659)
Adding to these is that local() has an option quiet=Bool to squelch command output in the logs.
However, local_resource() has no such option at all.
This inconsistency is unexpected and, at times, frustrating.
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
Locate the definitions and tests for local() and local_resource(), then compare how local() handles its quiet=Bool option. Done means local_resource() supports equivalent quiet behavior and the relevant tests cover the new option and its effect on command output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100