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
Once we have hints for the possible fixes of the path, we can try to show them on the state machine view, where a user can select one of the hints and we show it on the state machine highlighted (maybe in yellow, with dashes and with an animation of the dashes moving so we see it's like a possibility but not a fixed path).
Selecting a verifier hint and drawing that path, animated, on the diagram. Before this is possible:
Structured hints:HintDTO is only (kind, message). The verifier would need to send the calls of a call-sequence hint and the states it goes through, not just text, so the view never has to parse messages.
Mapping states: the hints are computed on the verifier's StateMachineBuilder, whose states are combinations of every @StateSet. The diagrams show one machine per state set (Show one state machine diagram per state set #163), so each combination must be projected onto the right diagram.
Incompleteness: when the machine is incomplete, the hints end with "(and possibly others)". The drawn path must read as one possibility, which is what the animated dashes are for.
The study: hints can give the answer away. Like the hints in the Verification tab, this stays opt-in, behind a click.
Activity