Summary: | Require plugins to specify the methods they implement | ||
---|---|---|---|
Product: | Koha | Reporter: | Tomás Cohen Arazi (tcohen) <tomascohen> |
Component: | Plugin architecture | Assignee: | Tomás Cohen Arazi (tcohen) <tomascohen> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | arthur.suzuki, dcook, magnus, martin.renvoize, olivier.hubert |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
See Also: |
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23890 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24632 |
||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: | |||
Bug Depends on: | 24631, 21073 | ||
Bug Blocks: | 23890, 23171 |
Description
Tomás Cohen Arazi (tcohen)
2019-05-02 15:43:31 UTC
Will the "interesting methods" always correspond to the plugin hooks that are in Koha? Or will there be cases where an "interesting method" is not in that list? If we are only looking for which plugin hooks a plugin implements, perhaps we could maintain a list of the hooks and filter the plugin_methods we have today against that list? We have discussed the possibility of a whitelist before... currently we have not done that so we can support legacy plugins which implement additional workflows via `/cgi-bin/koha/plugins/run.pl?class=plugin_class&method=X` (In reply to Tomás Cohen Arazi from comment #0) > I think plugins should just expose what methods they implement that are > intended to be used in Koha, not any internal method. Agreed. That would make it much easier to manage plugins. |