Timeline for Slashes in single route parameter or other ways to handle a menu tail with dynamic number of params
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 15, 2020 at 9:13 | history | edited | CommunityBot |
Commonmark migration
|
|
| Jan 4, 2016 at 23:18 | comment | added | Eyal | Of course you can use any encoding technique you want. I prefer JSON as it is very standardized with an encoder (/decoder) in most languages. This would make paths much less user friendly. If the path is exposed outside then I think passing the names in the query (name[]=Ben&name[]=George) is much more readable. | |
| Jan 4, 2016 at 22:50 | comment | added | rjacobs | Yes, encoding multiple arguments into one route parameter is certainly an option. I assume you are implying that the "names" param would be a formal php array that's directly encoded/serialized? If so, wouldn't there be more appropriate encoding options for a path component that JSON? Note that this would also make for a much less user-friendly path regardless of the encoding technique (a potential issue for human input, but not necessarily for programmatic path generation). | |
| Jan 3, 2016 at 23:37 | history | answered | Eyal | CC BY-SA 3.0 |