Allow storing block_classes_stored in state instead of config

Created on 16 August 2023, over 1 year ago
Updated 9 January 2024, 11 months ago

Problem/Motivation

Having classes added to any block stored for autocomplete is a nice feature but storing it in config tends to impact config workflow efficiency as it implies config changes to be potentially managed on every environment.
Eg when working on a local environment and adding removing classes for test purpose, leaves config changes even if we finally keep the block in it's initial state.

It would be great if we could choose to store those block_classes_stored in state instead of config. Considering the list of already used classes as content instead of config.

Feature request
Status

Needs review

Version

2.0

Component

Code

Created by

🇫🇷France ericdsd France

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024