I don't really know whether this feature should be implemented or not. I
solve this problem on my side using a separated list (e.g. foo,bar,baz)
as value. In my opinion this should not be part of the framework because
the implementing code needs also to verify the type for each parameter -
if somebody is kiddin', he enters an url like /foo/bar/id/5/id1337 - so
the script has also to check, whether the value is an array.
nickpdx schrieb:
The default way to turn a request parameter into a PHP array, is to name the
parameters using array notation:
/foo/bar?key[]=a&key[]=b
or
/foo/bar/key[]/a/key[]/b
The parameter name is "key[]" not "key". My initial reaction would be that
this same method would be used by the framework, that you'd get this
behavior for free because we're talking about PHP here. But, at least in
version 0.7.0, that doesn't appear to be the case. I'd be curious to know
if the router developers had taken this sort of behavior into account?
