Pro 6.0 b2 question: editing global colour `_id`

Fiddling around in the new Data store tools of the dev settings, I noticed that it was possible to change the _id of Global colours.

I am wondering if there is any downside of making a change to these? I appreciate it probably isn’t something that would ever be brought into the Global colours UI, but is there any issue with creating our own names for these, perhaps to make easier use of them in some situations, e.g. in some custom JSON looper providers or in custom components.

Being able to intuitively write them in as global-color:brand-primary would be awesome!

Presumably, changing the ID after they have already been in use throughout the site would need manual updating of any colour selection, but if it was set up at the very beginning of site build, would there be any problems?

2 Likes

@arthurodb, just keep in mind that if you’ve already assigned a color in a lot of spots it could create an issue with anything referencing it. But if you’re just building out a palette, you can certainly rename them and then set them up as default Parameter values like you’ve mentioned here. More of a power user kind of thing, but certainly doable.

3 Likes