https://bugzilla.wikimedia.org/show_bug.cgi?id=36309
Neill Mitchell <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #15 from Neill Mitchell <[email protected]> 2012-11-07 20:09:22 UTC --- Great that #set is coping with all chars :) I've tried an example similar to the original report. http://scratchpad.referata.com/wiki/User:Rotsee/set_test Has age has a number of allowed values: The allowed values for this property are: * [[Allows value::All]] * [[Allows value::1]] * [[Allows value::2]] * [[Allows value::3]] * [[Allows value::4]] * [[Allows value::5]] * [[Allows value::6]] * [[Allows value::7]] * [[Allows value::8]] * [[Allows value::9]] * [[Allows value::10]] {{#set:Has age=1,2,3,4,5,6,7,8,9,10}} does not work. This is an example of the original reason the bug was opened. #set no longer assigns multiple values. This works on SMW 1.5.6, but perhaps that was more luck that design (and I mean this in the nicest way!) In fact, stepping back here and thinking about it, perhaps it should not have worked. A string is a string. Looking back at the evolution of this bug, I think actually that Leonard's suggestion of a syntax extension may be the best solution here e.g. {{#set:Age value#list=1,2,3,4,5,6,7,8,9,10}}. In this way the ability to put any char into the #set is covered off and lists of values are also explicitly covered off. No grey areas! -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
