I found the problem, and then another one. And now it returns an error 500 with the description "[Object object]". I don't think this part of the service was in any use before
This is the situation: - There are routes /a and /b which return X and Y respectively - Both call the same function, but with one parameter different which determines if it's X or Y - The function filters the data two times (in the database query and afterwards with Array.filter()) to ensure it adheres to the parameter - I call /b, but it gives me X - The logs on that service confirm I called /b
Today is a "I call an external service and it should return X, but it gives me Y instead even though I looked at the code and there's no way it should do that" kind of day
Once again, someone called me on Teams while I was using my computer and there wasn't a single indication that it was happening. How do you fuck a core feature up so badly? Shit software.