Change Details

Currently the VirtualRESTService expects the `url` parameter to be a string. This forces users to encode path segments that might contain special characters (like slashes), and then forces us to potentially decode those path segments again in the backend to rewrite the URL. Instead, I think it would be nice to (also) support passing in an array of path segments: ``` uri => array( 'v1', 'local', 'page', $title, 'html', $oldid ) ``` What do you think?

Currently the VirtualRESTService expects the `url` parameter to be a string. This forces users to encode path segments that might contain special characters (like slashes), and then forces us to potentially decode those path segments again in the backend to rewrite the URL. Instead, I think it would be nice to (also) support passing in an array of path segments: ``` url => array( 'v1', 'local', 'page', $title, 'html', $oldid ) ``` What do you think?

Currently the VirtualRESTService expects the `url` parameter to be a string. This forces users to encode path segments that might contain special characters (like slashes), and then forces us to potentially decode those path segments again in the backend to rewrite the URL. Instead, I think it would be nice to (also) support passing in an array of path segments: ``` uriurl => array( 'v1', 'local', 'page', $title, 'html', $oldid ) ``` What do you think?