Story #4845: As a plugin API user subclassing pulpcore.plugin.content.Handler, I know which parts I can customize and which parts I can't - Pulp

Actions

Send by e-mail Copy link

Story #4845

closed

As a plugin API user subclassing pulpcore.plugin.content.Handler, I know which parts I can customize and which parts I can't

Added by bmbouter almost 5 years ago. Updated over 2 years ago.

Status:

CLOSED - DUPLICATE

Priority:

Normal

Assignee:

Category:

Sprint/Milestone:

Start date:

Due date:

% Done:

Estimated time:

Platform Release:

Groomed:

Sprint Candidate:

Tags:

Sprint:

Quarter:

Description

Ticket moved to GitHub: "pulp/pulpcore/1830":https://github.com/pulp/pulpcore/issues/1830

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?

Actions

Copy link

Updated by bmbouter almost 5 years ago

With subclassing I believe the non-changing interface are all public methods, and the possibly changing interface are private methods. We should sort the existing methods into these two categories as a start.

Actions

Copy link