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
Currently every nextTransition action/state/feedback needs to "know" the internal representation of GSD communication protocol. This can lead to both awkward and "brittle" code. Instead, the nextTransition group could be encapsulated as a class with functions to manage the key states in a more generic fashion.
I've already done this on my local repo and will submit with the PR addressing NextTransition issues.
Including Issues #45#54#55 and #66
The text was updated successfully, but these errors were encountered:
Currently every nextTransition action/state/feedback needs to "know" the internal representation of GSD communication protocol. This can lead to both awkward and "brittle" code. Instead, the nextTransition group could be encapsulated as a class with functions to manage the key states in a more generic fashion.
I've already done this on my local repo and will submit with the PR addressing NextTransition issues.
Including Issues #45 #54 #55 and #66
The text was updated successfully, but these errors were encountered: