As a plugin API user subclassing pulpcore.plugin.content.Handler, I know which parts I can customize and which parts I can't
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
Author: @bmbouter (bmbouter)
Redmine Issue: 4845, https://pulp.plan.io/issues/4845
Problem.
It's not clear which methods of the pulpcore.plugin.content.Handler object should be customized versus use as is. Here are some questions I'm interested in:
Are they all safe to customize?
Do some methods depend on other methods in ways that customization may cause breakages?
Are these methods the right way to position this Handler?
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 pulpcore.plugin.content.Handler and review its methods and their relationships. Document which methods plugin API users may customize, which should be used as-is, and how customization affects Handler positioning; the issue provides no test or validation entry point.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100