Theme block JSON preset validation

[charlespwd]

Maybe duplicate of what @navdeep5 is doing?

Should we add a tasklist in here?

Or a duplicate of #602

Top of mind:

Tasks

Preview Give feedback

1. Make sure setting id/value pairs in presets match the block
2. Make sure block type is accepted by parent
3. Preset names can be a translation key. Show an error when this translation key does not resolve to a value. (can share overlap to the work done for verifying schema name value). This validation should work for section presets as well.
4. ... ?

[bakura10]

I think this is somehow related. But since theme blocks are introduced (I think) we can now connect a block value as a default. For instance, inside a section, I have this block:

"blocks": [
    {
      "type": "collection",
      "name": "t:sections.featured_collections.blocks.collection.name",
      "settings": [
        {
          "type": "collection",
          "id": "collection",
          "label": "t:sections.featured_collections.blocks.collection.collection"
        },
        {
          "type": "text",
          "id": "title",
          "label": "t:global.text.title",
          "default": "{{ block.settings.collection.title }}"
        }
  }
]

This is convenient and allow to automatically connect the title with the collection's title of the block.

Theme check report does not currently allow that though:

I am not sure if this is expected @charlespwd

[charlespwd]

Hmm that's def a bug. Looks like Liquid in {% schema %} is being visited but shouldn't be.