Null coalesce in AttributeMapper instead of try/catch#615
Merged
roxblnfk merged 1 commit intoMay 12, 2025
Merged
Conversation
…mplify error handling by using null coalescing instead of try-catch blocks. This improves code readability and maintains functionality.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
roxblnfk
approved these changes
May 11, 2025
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.
This PR related to the discord discussion about a bug where error handler can be reassigned so this error is not being caught.
null-coalesce will serve the same purpose here and will not rely on try/catch