CustomValues

[GoogleCodeExporter]

Use of CustomValues is high on the list (left and right part of rule as well).

Still some thinking about the syntax format needed.

May be something like:

<<Custom(MyCustomValue).Contains:abc>>

Original issue reported on code.google.com by rainer.c...@googlemail.com on 19 Apr 2013 at 7:34

[GoogleCodeExporter]

how about <<Custom.Contains([CustomKeyName], abc)>>

this way you're not upsetting the "Key.Modifier" logic

Original comment by NiceziaVincent on 27 Apr 2013 at 3:54

[GoogleCodeExporter]

well, actually I meant:

<<Custom([CustomKeyName]).Contains:abc>>

That would fit nicely in the logic:

<<[key].[modifier]:[value]>>

wouldn't it?

Original comment by rainer.c...@googlemail.com on 27 Apr 2013 at 4:06

[GoogleCodeExporter]

it sort of demands a new parsing method though

Original comment by NiceziaVincent on 27 Apr 2013 at 5:07

[GoogleCodeExporter]

you see i mistyped mine

it was supposedf to be 
<<Custom.Contains:[CustomKeyName], abc>>

Original comment by NiceziaVincent on 27 Apr 2013 at 5:10

[GoogleCodeExporter]

but no really big deal on my side. It's up to you...

Original comment by rainer.c...@googlemail.com on 27 Apr 2013 at 5:10

[GoogleCodeExporter]

as each custom key is a field of its own I really would prefer:

<<Custom([CustomKeyName]).Contains:abc>>

This way I'm sure that the field name is stored before the modifier. Makes
it easier for me. Any problems with the GUI that way? Nevertheless, there's
no need to hurry.

2013/4/27 Rainer Clodius <rainer.clodius@googlemail.com>

Original comment by rainer.c...@googlemail.com on 27 Apr 2013 at 5:14

[GoogleCodeExporter]

Honestly, i thought it might be a problem (me having to re-write my parsing 
code, but i just nailed that down in the time it took for you to respond (so 
yeah if you want you can release it that way 
<<Custom([CustomKeyName]).Contains:abc>>

Original comment by NiceziaVincent on 27 Apr 2013 at 5:19

[GoogleCodeExporter]

so you already started coding it that way?

Thought it might be easier to parse:

<<Custom([CustomKeyName]).Replace:abc, def>>
than
<<Custom.Replace:[CustomKeyName], abc, def>>

Original comment by rainer.c...@googlemail.com on 27 Apr 2013 at 6:30

[GoogleCodeExporter]

... especially when people may put some strange characters like commas etc. in 
the name of the custom key. I know what evil lurks in the heart of men ;)

Original comment by rainer.c...@googlemail.com on 27 Apr 2013 at 6:43

[GoogleCodeExporter]

So True

Original comment by NiceziaVincent on 27 Apr 2013 at 6:56

[GoogleCodeExporter]

fixed in 1.0.7

Original comment by rainer.c...@googlemail.com on 14 May 2013 at 8:39

• Changed state: Fixed