https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21073 Martin Renvoize <martin.renvoize@ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |martin.renvoize@ptfs-europe | |.com --- Comment #47 from Martin Renvoize <martin.renvoize@ptfs-europe.com> --- (In reply to Tomás Cohen Arazi from comment #15)
Proposal for discussion: - Make it explicit by declaring what 'capabilities' the plugin has, like our $capabilities = { tools => 1, ... }; - Rename methods => capabilities: CREATE TABLE IF NOT EXISTS plugin_capabilities ( class varchar(255) NOT NULL, capability varchar(255) NOT NULL, PRIMARY KEY ( `class` (191), `capability` (191) ) ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
I sort of like the idea behind this (very much borrowed from ILL backends ;) ), but I'm happy for it to wait for another patch if we deem it's helpful. I do however note we're currently loading all class methods into the database.. do we perhaps want to restrict them to 'public' methods only (i.e. missing out _method methods) or even limit down to only 'supported' methods known by the plugin system? (I'm not sure about the latter.. we might want to allow a plugin to introspect itself for some reason in the future... perhaps?) -- You are receiving this mail because: You are watching all bug changes.