-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enhancing Course Search #105
Comments
Also a minor quality of life update that may be nice is if when you use the back button or redirect to homescreen utilizing the poly logo it keeps the search type to |
As far as the first problem goes, it could be as simple as using a regex—like Trying to dynamically determine whether to search by professor name or course probably wouldn't be too difficult either, but there's probably some non-trivial React-ing that needs to happen to save the search state between page navigations to/from the homepage and search page. I'd defer to @mfish33 or @cjlawson02 on the level of effort though.. |
I see, for now I would like to look into the regex implementation. Could you point me in the direction of where the searchbar input is parsed? |
Hi @lab596, thank you for the bug report. I just opened a PR #111 to fix the second issue. It was not directly related to the state being saved but was a great opportunity to fix some poorly written code that has been around since the beginning of the site. The code used to filter options for the user resides in two places.
I like the improvement around courses showing up with or without the space included but I am unsure about combining course and name suggestions to the user. Without clear UI/UX I think that this could easily get confusing |
Ok that makes sense |
Hey, I noticed that if you search for a specific course without a space in between the number and the course it provides a no results page. Can we have it so either no space in between the department or a space in between provide the same results?
Is something like this possible?
The text was updated successfully, but these errors were encountered: