fix: handle null memos in getActiveJobs to prevent runtime error#194
Open
Kubudak90 wants to merge 1 commit intoVirtual-Protocol:mainfrom
Open
fix: handle null memos in getActiveJobs to prevent runtime error#194Kubudak90 wants to merge 1 commit intoVirtual-Protocol:mainfrom
Kubudak90 wants to merge 1 commit intoVirtual-Protocol:mainfrom
Conversation
Add optional chaining (?? []) when mapping job.memos to prevent TypeError when memos is null or undefined from API response. Fixes Virtual-Protocol#10
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
1 participant
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.
Fixes #10
Problem
When
job.memosis null or undefined from the API response, calling.map()throws a TypeError.Solution
Add optional chaining with nullish coalescing:
(job.memos ?? [])Changes
Testing
All 50 unit tests pass.