Add token syntax validation where possible
Problem/Motivation
We often have the case that users are confused / accidentally use token brackets on token name configuration inputs. When a token name is required, the the correct syntax would be "my_token" and not "[my_token]". However, the latter one is often being set instead.
Affected token name user input fields are following configuration keys:
- token_name
- list_token - we found out here #3352393: New condition: Contains for lists that this was not the ideal choice
Steps to reproduce
Proposed resolution
Since the current decision is to not support tokens in token name inputs #3302569: Add token support to fields "token_name" we may consider that the token name input fields can also work with the bracket syntax - although not officially supported. That would be a bit more versatile.
Remaining tasks
User interface changes
API changes
Data model changes
Edited by drupalbot