Fix#446 Treat Number Keys as Valid Keys in the set Function#447
Open
nightohl wants to merge 3 commits into
Open
Fix#446 Treat Number Keys as Valid Keys in the set Function#447nightohl wants to merge 3 commits into
nightohl wants to merge 3 commits into
Conversation
- Ensure number keys are treated correctly as part of the path - Modify path parsing to correctly handle numeric keys as object properties
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
- Add checks to prevent invalid paths like empty strings or '[]' - Ensure correct behavior when path is just a number index
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.
Description
Checklist
package.jsonhas been bumped (matching semver)yarn buildcommand has been run and to update thecdndirectory/docsdirectory) has been updatedResolves
If the PR resolves an open issue tag it here. For example,
Resolves #34