We had a slash in a program location ("Hospitality (room 106/107)"), and selecting that location in the filters caused an error:
The page /loc/Hospitality%20(room%20106/107) was not found.
I noticed while investigating this that no error is generated for other special characters (e.g. "Other (room 101)" works fine), or if the location does not, in fact, exist in the schedule (you get a list of 0 items).
I found some old related issues in react-router, but it's unclear to me what the current expected behavior is for slashes, or whether there's an appropriate way or place to escape them to get such an ID to work.
My workaround was to rename the location at the source.
We had a slash in a program location ("Hospitality (room 106/107)"), and selecting that location in the filters caused an error:
The page /loc/Hospitality%20(room%20106/107) was not found.I noticed while investigating this that no error is generated for other special characters (e.g. "Other (room 101)" works fine), or if the location does not, in fact, exist in the schedule (you get a list of 0 items).
I found some old related issues in react-router, but it's unclear to me what the current expected behavior is for slashes, or whether there's an appropriate way or place to escape them to get such an ID to work.
My workaround was to rename the location at the source.