Open luminousleek opened 2 years ago
Thank you for this bug report. But we would like to let you know that this is the expected response. As faculty for NUS students is predefined in the app whereas skills/frameworks/languages/tags are user defined Therefore the app does not recognise an incorrect faculty but will show output for non-existing skills/frameworks/languages/tags
Team chose [response.Rejected
]
Reason for disagreement: The bug is that these two cases are handled differently, which is not expected by the user. It should not matter if this is how the features were designed, because the end result is still an inconsistent handling of invalid inputs.
Bug: Trying to filter with a non-existent faculty gives a "Faculty not found" error, but trying to filter with a non-existent skill/language/framework/tag gives 0 people in the filtered list
Steps to reproduce:
filter f/asdf
, and thenfilter fr/asdf
Filtering wrong faculty:
Filtering wrong framework:
Before filter:
After filter: