Fix config schema

Let's do that in the 2.x version.

Hello @Grimreaper I think we can also implement a settings form to changes de settings defined in the schema file.

Another thing we should add a menu link to get access to this form.

What do you think?

Hi I just added a basic schema but we have a lof of work to do, please answer my previously comment and the we can move to next steps

The basic schema added is incorrect. So this needs a new start.

Grimreaper → changed the visibility of the branch 3336970-fix-config-schema to hidden.

Grimreaper → closed merge request !40

I wonder if empty prop should be saved.

Moved to beta2 because July is too early

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

All tests are green now with strict schema validation. I also added schema validation to kernel tests so every source plugin is tested now. Happy about review.

All tests are green now with strict schema validation. I also added schema validation to kernel tests so every source plugin is tested now. Happy about review.

Pipeline is red.

I made some review comments. In some comments, I said I need to check, so they are on my side.

I have tested with ✨ [10.1.x] Upgrade to UIP2 Active . Almost there! Thanks!

2 remaining points that I got multiple times:

This one is due to my custom field formatter in Sobki, on my side then:

This one is due to my source plugin in ui_styles_ui_patterns, on my side then:

Ok you fixed variant ID by the time I made my tests. :)

I add nullable to component_id. This is needed for layouts

We have problems with 2 source plugins. ui_patterns_source.block and ui_patterns_source.entity_field
The problem is that one dynamic configuration key.

source:
   block_id: 'block_name'
   block_name: 

I can't use block_name in my mapping because it is dynamic . Better would be a configuration like:

source:
   block_id: 'block_name'
   configuration:
       block_name: 
      ...... 

Here I can configure configuration as a sequence.

The most important is to not introduce breaking changes now. Shipping with a loosely defined schema is better than a breaking change in RC.

Auto-merge

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