Project

Profile

Help

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

Added by bmbouter 2 days ago. Updated 2 days ago.

Status:
NEW
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
% Done:

0%

Platform Release:
Blocks Release:
Backwards Incompatible:
No
Groomed:
No
Sprint Candidate:
No
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:

Description

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?

History

#1 Updated by bmbouter 2 days 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.

#2 Updated by bmbouter 2 days ago

  • Description updated (diff)

Please register to edit this issue

Also available in: Atom PDF