fix: prevent DataAmount crash by guarding dataSize access#16
Open
rahul810050 wants to merge 1 commit intooaiedu:masterfrom
Open
fix: prevent DataAmount crash by guarding dataSize access#16rahul810050 wants to merge 1 commit intooaiedu:masterfrom
rahul810050 wants to merge 1 commit intooaiedu:masterfrom
Conversation
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.
Fixed issue: #15
Summary
This PR fixes a dashboard crash caused by unsafe access to nested
dataSizeproperties in
DataAmount.vuebefore Firestore data is fully loaded.Root Cause
dataSizeis set asynchronously. During initial render, nested fields suchas
questions.generalmay be undefined, leading to runtime errors.Changes
DataAmount.vueto derive all values via computed propertiesResult
Before:
After:
