Parser for I/O customization rule is too strict. about root

[Kamakshi8104]

hey can I work on this issue?

[gemmeren]

I am looking into this for Fixarhon. No promises.

[gemmeren]

I believe before line: L198
one needs to insert:
command = TSchemaRuleProcessor::Trim( command );
Still struggling with running a reproducer :(

[gemmeren]

Of course, its not quite as easy... :(
The parsing currently looks for }" without any white-space, similarly it checks for the 2nd character to be the { , meaning no space between the quote and brace here either. I'd suggest:
Split off the quotes, trim the string and check the first and last characters to be { and }. But I am not totally convinced that this may not have bad side-effects...

[gemmeren]

I need to rethink this, since my initial PR lost command elements after code key. Part of the problem is code fragment can include either curly braces or quotes, so finding the end of the key isn't quite as trivial. Since any end marker could be allowed as legal piece of code, limiting things to the current }" may actually be the most proper.