This response doesn't really make sense, anyone have any idea why it's happening?
The response for that filter query should really be something like
["COMP 248","COMP 249"]
I think it's pretty cool that you can put special characters into the search filter, but we should definitely look into whether there are security concerns (a la SQL injection) with this feature. If we want to keep supporting special characters (I think it accepts any regex, but I'm really not sure), then we should definitely make sure the correct results are returned.
If you perform the following api request:
The server returns the following response:
This response doesn't really make sense, anyone have any idea why it's happening?
The response for that filter query should really be something like
I think it's pretty cool that you can put special characters into the search filter, but we should definitely look into whether there are security concerns (a la SQL injection) with this feature. If we want to keep supporting special characters (I think it accepts any regex, but I'm really not sure), then we should definitely make sure the correct results are returned.