Proposal: An event model
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.2k
- Forks
- 1.7k
- Avg merge
- 13d 8h
- Merged PRs (30d)
- 2
Description
imo it would be handy if there was an event model, eg for such:
actors_labels = event.actor.labels
in contrast to the current:
event_properties = parse_event(event_string)
container_id = event['Actor']
actors_labels = client.containers.get(container_id).labels
which turns against the dry-paradigm quickly.
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 the current event string parsing and container lookup described in the issue, including the event properties and Actor references. Define the model's intended event and actor interfaces first; done would mean callers can reach actor labels through the proposed event model without repeating the current parsing and lookup sequence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100