The current implementation of DialogStateMachine in the dialog_state_machine.py file restricts state transitions to predefined states configured by the developer. It is not possible to directly change the dialog state to an arbitrary value, like "/rock", using only the action parameter without modifying the library code.
This limitation hinders the flexibility of the dialog system and requires developers to modify the library code to add new states or allow arbitrary state changes. It would be beneficial to provide a way to extend or customize state transitions without modifying the core library code.
Please consider improving the flexibility of state transitions in the DialogStateMachine class to allow developers to easily add new states or transition to arbitrary states without the need for library code modifications.
The current implementation of DialogStateMachine in the dialog_state_machine.py file restricts state transitions to predefined states configured by the developer. It is not possible to directly change the dialog state to an arbitrary value, like "/rock", using only the action parameter without modifying the library code.
This limitation hinders the flexibility of the dialog system and requires developers to modify the library code to add new states or allow arbitrary state changes. It would be beneficial to provide a way to extend or customize state transitions without modifying the core library code.
Please consider improving the flexibility of state transitions in the DialogStateMachine class to allow developers to easily add new states or transition to arbitrary states without the need for library code modifications.