New plugin event : PluginEnabledEvent

[sgirard84]

I think this event would be nice.

In case the plugin need to do some actions after the installation.

[giuscris]

I think it's a good idea, indeed I chose to tackle the development of this kind of events in a second moment.

The question is: what should be the naming for the handler method? onPluginEnabled is dispatched by every plugin after their activation.
I think we can call it onSelfEnabled, does this make sense?
By this convention why don't we add onSelfDisabled and other lifecycle events? Just need to think about use cases.

[sgirard84]

I think it make sense

I'm working on a sqlite plugin to store "non-pages" data. My event booking website is currenty using regular pages to store each event attendee. But I'll move this kind of data in small sqlite file database (easier to store, read, search, run reports, etc).

A plugin that use this sqlite plugin will have a scripts folder. On plugin enabled, a script will run to create the tables if they do not already exist, to prepare the plugin functionnality.

In that case, I will not need onSelfDisabled event but still a good idea.

[giuscris]

Do you really need a scripts folder? The initialization could be done inside a class that handles the database also for storing/reading. You could then use the composer autoloading.

[sgirard84]

I'm trying to not do this validation each time the plugin is loaded.
But thanks for the idea, I'll see what composer can do and handle this.

[giuscris]

I'm assuming you are calling the validation code in the new event, of course.