The match-set token signaled when part of a path should consider more than one value - when resolving a Flow path/query. An example of match-set token usage follows:
The hard brackets () were used to indicate that the path/query part had multiple options.
Since the path syntax prohibits a token or state name from including the pipe-character, I think the presence of a pipe character is enough to indicate that there are multiple options. The wrapper feels unnecessary.
Without brackets, the initial query would now look like so:
While there is less structure to this form, it should result in a reduced amount of parsing overhead, and symbol noise.
Closes #31 - multiple tokens no longer need brackets ("")
Re #20 - Added query token lists and child-states tests
Removed (direct) genData dependency