Repository navigation
Fix no-rows bug with last message status - #4061
Merged
Merged
Conversation
AlaricWhitney
approved these changes
Sep 9, 2024
KatieMSB
approved these changes
Sep 9, 2024
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
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 l
30F1
ine 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.
This pull request improves the error handling for validation in GraphQL. It includes a fix for a bug where the LastMessageStatus function was returning an error when there were no rows found in the database. Now, if the query returns no rows, the function will return nil instead of an error. This improves the overall error handling and ensures a smoother experience when working with GraphQL validation.