Backwards compatibility for attributes

[ouun]

Hi @Log1x,

while I tested PR 315 I also worked with your latest commits.
There seems to be an issue right now with the $align_text param. The css classes are not outputted as required.

    /**
     * The default block text alignment.
     *
     * @var string
     */
    public $align_text = 'center';

I checked the docs and realized that for setting the default value it requires something like this:

$block['attributes']['style'] =  [
      'type' => 'object',
      'default' => [
          'typography' => [
              'textAlign' => $this->align_text,
          ],
      ],
  ];

I am not able to deep-dive into this right now, however I hope it is of any help.

[Log1x]

appreciate you testing this. i figured there was definitely a bug or two, wasn't confident in a release yet. 🙈

should be an easy fix.

[davidwebca]

When using the native "supports" for backgroundColor, text color and gradients, in a block.json, it's possible to have a pre-selected default color for them like this:

"attributes": {
    "backgroundColor": {
        "type": "string",
        "default": "red"
    }
}

So that when adding a new blank block, these attributes are already filled.

Is this something that's already possible here? I can't seem to find the correct way so that my generated block.json has the attribute when running wp acorn acf:cache 🤔

[Log1x]

Not at the moment without overriding https://github.com/Log1x/acf-composer/blob/master/src/Block.php#L412 and calling the parent/merging. Definitely something that could be improved.