You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Feature Request
I mentioned this in my autocomplete request, but I think it deserves its own issue...
It would be useful to have an "Event" view. Something that gathers all instances of <transition>, <send>, and <raise> event names and allows sorting them. As my state machine gets more complex, it becomes more difficult to keep track of the event names that I've used, and a consistent naming convention. It'll be even more difficult for somebody new to the project trying to figure out what events are available.
I imagine the view having the following sort modes, with similar layout to the structure view:
Sort by unique name - each name then expands to the transition/send/raise events that invoke it
Sort by transitions - expands to state/send/raise that invoke it
Sort by send/raise - expands to the transitions invoked by it
Have some way of highlighting events that have no transitions or no send/raise associated with them (these might be intended to be external, but they could also be spelling mistakes)
The text was updated successfully, but these errors were encountered:
Feature Request
I mentioned this in my autocomplete request, but I think it deserves its own issue...
It would be useful to have an "Event" view. Something that gathers all instances of <transition>, <send>, and <raise> event names and allows sorting them. As my state machine gets more complex, it becomes more difficult to keep track of the event names that I've used, and a consistent naming convention. It'll be even more difficult for somebody new to the project trying to figure out what events are available.
I imagine the view having the following sort modes, with similar layout to the structure view:
Have some way of highlighting events that have no transitions or no send/raise associated with them (these might be intended to be external, but they could also be spelling mistakes)
The text was updated successfully, but these errors were encountered: