I thought of it, but I don't know… on one hand it indeed allows accessing a lot more stuff if need be, and we could even make sure the extension got unregistered on plugin unload (so a plugin forgetting to unregister wouldn't crash, although I wouldn't love authors to disregard deregistration), but it also means that it's not possible to discriminate several extensions registered by a single plugin, which might (or might not) be an issue for e.g. Peasy-based plugins (not that I can tell whether this API is Peasy-friendly to begin with).

Oh sure, multiple extensions provided by a single plugin - we must have that! :-)

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.