Investigate possible improvements to the implementations of manifest fields
Open
Nobody has claimed this yet.
Task
- Dominant language
- Python
- Stars
- 31
- Forks
- 56
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 22
Description
This is a follow-up of review comments:
https://github.com/pulp/pulp_container/pull/1782#discussion_r1824259956
https://github.com/pulp/pulp_container/pull/1782#discussion_r1824242918
We could investigate the feasibility of the suggested improvements:
- merge the os/arch/size/metadata manifest methods to prevent incorrect updates of these fields
verify if adataclasstogether withasdictwould be helpful for the manifest fields defined fromplatform
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 with the linked review discussion on pull request 1782 and trace the manifest field implementations it refers to. Determine whether the os, arch, size, and metadata methods can be merged without incorrect updates; done means documenting or implementing a justified approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100