confusion when config/enabled_resources filters a resource
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Description
I've had a couple debugging sessions that went like this:
- We added a new local_resource to the Tiltfile
- The resource didn't show up in the sidebar
- MADNESS
- Oh, wait, enabled_resources is hiding it
Seems like we should have some way to display when resources are being filtered, e.g.,
During tiltfile execution, log the names of the disabled resources
Some UX in the sidebar like '5 resources disabled, click here for more'
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 tracing how config/enabled_resources is applied during Tiltfile execution and how the sidebar receives its resource list. Define a user-visible indication for filtered resources, then verify that users can identify which resources are disabled and why.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100