Fix date-time parse error handling and return 400 API response instead of 5xx#231
Merged
Conversation
aracho1
force-pushed
the
ac/fix-error-code
branch
2 times, most recently
from
July 17, 2026 11:20
9e420fa to
d654d2d
Compare
aracho1
force-pushed
the
ac/fix-error-code
branch
from
July 17, 2026 11:55
d654d2d to
4a934a5
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What does this change?
SaveArticlesController, when a client sends a date string that doesn't match the expected date/time format (ISO), the exception isn't caught anywhere in the request-handling chain so it propagates as an unhandled failure, crashing the lambda and causing API gateway to return 502 instead of the correct 400 error.How has this change been tested?
Tested on CODE