Proposal: Consider storing container name in Container struct
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 132
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Description
Currently, the Container struct stores the container ID, short ID, image, exposed ports, and runtime state, but it does not include the container name.
I was wondering whether the omission of the container name is intentional. In some scenarios, having the name available directly on the struct could be useful, particularly for debugging and improving log readability.
Before opening a PR, I wanted to ask whether this was intentionally excluded to keep the abstraction minimal, or if adding a name string field to the struct would be considered acceptable.
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
This issue is a proposal about whether Container should include a name field, but it names no file, test, or entry point. First wait for a maintainer decision on the abstraction; implementation scope and completion criteria are not yet defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100