Collect as Search

[auriium]

Related to #12

When searching through nodes searchinfo should add the entire physical fucking node and add it to itself somehow preserving relationship in order to offer block to user

[auriium]

Searching /command subgroup literal argument optional should gather:

NOTE THE DISTINCTION BETWEEN STRINGS AND BLOCKS: Strings are popped from the string queue as parsing goes on.
Blocks are added to the block stack as parsing goes on. The two are inversely proportional

Remaining strings before postparsing (queue: argument -> optional)
Remaining strings after postparsing (queue: empty)
{in this case postparsing performed by argument node literal}

Gathered blocks before postparsing (queue: command -> subgroup -> literal)
Gathered blocks after postparsing (queue: command -> subgroup -> literal -> argument -> optional)

A realistic simulation of this command would be

/kitpvp users ban required:name [optional:time]

[auriium]

Essentially, as parsing goes on, blocks should be added as strings are removed.

I'm debating whether to only add blocks or whether to also add entire fucking nodes (unsafe) with a deprecated method to the searchoutput (gonna be renamed SearchCrawler)

The search direction goes in this order: SearchInput -> SearchCrawler -> (get) Execution