Fix propName error in normalizeProps when props array contains non-empty string values#154
Open
MatrixNeoKozak wants to merge 1 commit into
Conversation
…pty string values
|
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.
The
normalizePropsfunction incorrectly useszipObjectwith only keys, resulting in prop values beingundefinedfor all props passed as arrays. This causes runtime errors when props are expected to have default values or types. The fix usesArray.reduceto properly create an object with keys mapped to empty objects (the Vue convention for minimal prop validation). Also removeslodash.zipobjectdependency entirely.