Closed
Description
Given the following workflow config:
transitions:
some-transition:
from: some-state
to: some-other-state
Causes the transition to be created with the name some_transition
without any warning whatsoever. I guess its the Configuration
's fixXmlConfig
that does this, so i guess it would affect other config areas as well, where you are free to choose a key and the configured component/bundle/module allows for -
in such names.
Transitions explicitly allow the usage of -
in transition names.
Currently this can be avoided by not using the keyed transition config, but the array like config
transitions:
- name: some-transition
from: some-state
to: some-other-state
If this cant be fixed, it would be nice to deprecate the keyed transition config and only allow the array style.