Last modified: 2013-01-06 11:55:01 UTC
Don't you object if `0' and `1' are accepted as valid values for boolean arguments? It simplifies a bit my application. Trivial patch will be attached soon.
Created attachment 9485 [details] Trivial implementation.
Which extension is this? Maybe this one: http://www.mediawiki.org/wiki/Extension:Validator
Applied in r103602. Vdb: Don't know if you are interested in poking at this, but the ParameterInput could use some nicer handling of boolean values. Right now it creates a dropdown with on, off, yes and no (and now 0 and 1 as well) instead of some checkbox or so. Either way, it should not have redundant values. (It's used on special:ask)
> Which extension is this? Maybe this one: > http://www.mediawiki.org/wiki/Extension:Validator Yes. `Validator' is not present in a list of extensions, so I had to select `[other]'. > Vdb: Don't know if you are interested in poking at this, but the ParameterInput > could use some nicer handling of boolean values. Right now it creates a > dropdown with on, off, yes and no (and now 0 and 1 as well) instead of some > checkbox or so. Either way, it should not have redundant values. (It's used on > special:ask) Sorry, did not get. I do not use `0' and `1' as primary input. Indeed, boolean variable, being inserted to text, looks either as `0' or `1'. So, accepting `0' and `1' allows do not care about boolean values, and do not convert it to `yes' and 'no' every time they go to text. Moreover, `0' and `1' are not case-sensitive and language dependent. Do you mean I should pay attention to ParameterInput and fix it?
This is about an issue you did not cause, but is made somewhat worse by adding more values that get accepted by the boolean type. I'm just pointing out this is some bit-sized thing you could also fix if you'd like to.
Ok, will look at that next week.
