[2.0.0-alpha1] Source plugins:methods naming and interfaces use

Use PluginFormInterface::buildConfigurationForm() in source plugins instead of SourcePluginBase:buildSourceConfigurationForm(), moving the wrapping of SourcePluginBase::buildConfigurationForm() into the form builder. So, every expected methods in a plugin class belong to a defined interface

It is currently done in 📌 [2.0.0-alpha1] Add new Form Builder Needs work

this one was resolved by the new interface:

Last question: "ContextAwarePluginInterface methods are not used by the Form Builder, only internally by SourcePluginBase. is it normal ?"

Also: add default "value" key in each source plugin forms.

Like content field properties, there is always at least a key, and this one is "value" by default.

Christian.wiedemann → made their first commit to this issue’s fork.

After rebasing 📌 [2.0.X-alpha1] Introduce buildComponentRenderable Needs review , there are a few issues left:

• variant selector is not working: variant selection is not saved and retrieved
• after refreshing the page, all the form is reset expect the component selector

Automatically closed - issue fixed for 2 weeks with no activity.