Why is this an issue?

Sharing some naming conventions is a key point to make it possible for a team to efficiently collaborate. This rule allows to check that all FSM states match a provided regular expression.

How to fix it

Code examples

Noncompliant code example

With default regular expression: ^[A-Z]+[A-Z\\d]*$

architecture rtl of fsm is
  type my_enumerated_type is (dream, fly, run, sleep); -- Noncompliant (lowercase)
  signal state : my_enumerated_type;
  ...

Compliant solution

With default regular expression: ^[A-Z]+[A-Z\\d]*$

architecture rtl of fsm is
  type my_enumerated_type is (DREAM, FLY, RUN, SLEEP); -- Compliant (uppercase)
  signal state : my_enumerated_type;
  ...