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 5 months ago. Updated about 1 month ago.

Status:
NEW
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% 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 5 months 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 5 months ago

  • Description updated (diff)

#3 Updated by bmbouter 3 months ago

  • Sprint/Milestone set to 3.0

This needs to be finalized or plugin writers could receive breaking changes post 3.0 GA

#4 Updated by daviddavis about 1 month ago

  • Sprint/Milestone deleted (3.0)

Please register to edit this issue

Also available in: Atom PDF