-
Notifications
You must be signed in to change notification settings - Fork 0
ASPC-35: Fixed grad requirement filter to be compatible with newer updates (and added toggle + warning) #147
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
base: main
Are you sure you want to change the base?
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
| page = 1, | ||
| } = req.query; | ||
|
|
||
| const requirements = req.query.requirements |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you shoudl be putting it in the req.query object and handling it from there
backend/src/routes/CoursesRoutes.ts
Outdated
| } | ||
|
|
||
| // Get fuzzy matches using aggregation | ||
| const fuzzyMatch: any = { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
add requirements to search stage instead of adding another fuzzyMatch function to be consitent with our code. if there is a specfiic reason you did this way, lmk
haram082
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: u never addressed "you shoudl be putting it in the req.query object and handling it from there"" but it's not a big deal. the filtering logic you updated looks good. feel free to merge
Context
Describe your changes
Testing
Screen.Recording.2025-11-08.at.9.52.25.PM.mov