SearchAlg code with fixed Linter issues #27
Conversation
|
Reverting changes from my search.js file because i had a lot of recent test failures stemming from changes made to the search API, particularly in handling user, message, and utility methods. I went back to the OG code and tried to fix it but kept getting some errors - specifically, the errors related to unexpected status codes (400 instead of 200), improper error handling, and issues with modifying global objects like navigator in the test environment. I went through them and these modifications introduced inconsistencies and were causing regressions though not sure why. To pass the tests and go back to a stable codebase, I am reverting these changes and returning to the original logic. going to be ensuring the search API handles requests correctly with expected status codes and outputs. Additionally, mocking techniques will be used to handle environment-specific objects like navigator in utility tests. This reversion i think will maintain compatibility with the test framework while ensuring functionality remains intact and everything is passing now so looks good. |
|
Good descriptions for context! Everything looks good to me |
Removed trailing spaces and fixed tabs and spaces issues