we must prepend ">>" at the beginning of the string in order to tell Siesta that what follows should be resolved as a component query.
It would be great if Siesta would automatically determine that this should be a component query by the fact that 'target' is a string and doesn't contain '=>'.
This would simplify things since in most cases, since most of the time a component query is desired.
This will conflict with the fact that Siesta should be a generic web/JS tool. The default should be a CSS query so there is no easy way around this I'm afraid. If this is critical for you, you could hot-patch our source where the resolving is made.
