Deprecate the match-set token's bracket wrapper ("[]") #31

Closed
bemson opened this Issue Apr 2, 2013 · 0 comments

1 participant

@bemson
Owner

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:

someFlow.query('//here/[foo|zee|there]/everywhere/');

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:

someFlow.query('//here/foo|zee|there/everywhere/');

While there is less structure to this form, it should result in a reduced amount of parsing overhead, and symbol noise.

@bemson bemson was assigned Apr 2, 2013
@bemson bemson added a commit that closed this issue Apr 10, 2013
@bemson Closes #31 - multiple tokens no longer need brackets ("[]")
Re #20 - Added query token lists and child-states tests
Removed (direct) genData dependency
2288c06
@bemson bemson closed this in 2288c06 Apr 10, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment