Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have been noticing a lot of noise in the server logs recently with a lot of 400 Bad Request errors. I'm pretty sure those are from the snoowrap library (which I just found out has been archived), but I wasn't sure why there were so many of them. I dug a little deeper and found the errors being logged from files that didn't even interact with the library and realized that I each logger was logging unhandled exceptions and rejections, so there were a dozen entries for each error. I refactored the way logs are created, so that only the INDEX one tries logging unhandled exceptions/rejections.
Sorry for the noise in this CL, but I tried setting the line length in the Prettier config to shorter than the ESLint config, and it did a much better job of placing line breaks, so we only need 3 of the
max-len
statements in the app. By running Prettier -> ESLint, it did a lot of reformatting to the files, but the only files I changed the logic in are logger.js and index.js (to pass the new params). You should be able to safely ignore the remaining files.