fix: check if property exists before using them#9
Merged
megatank58 merged 1 commit intogominima:mainfrom Feb 15, 2022
booleanrecep:fix-undefined
Merged
fix: check if property exists before using them#9megatank58 merged 1 commit intogominima:mainfrom booleanrecep:fix-undefined
megatank58 merged 1 commit intogominima:mainfrom
booleanrecep:fix-undefined
Conversation
|
✔️ Deploy Preview for gominima ready! 🔨 Explore the source changes: 1a11bf5 🔍 Inspect the deploy log: https://app.netlify.com/sites/gominima/deploys/620ab1b4e31b510008a6e5a7 😎 Browse the preview: https://deploy-preview-9--gominima.netlify.app/ |
Contributor
|
Seems like the main repository did not have these documented in comments so it wasn't present, good catch, however the code block will now be empty, can you tell the page on which the errors occur? |
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 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.
Solved errors shown below with Optional chaining (?.):
2.