{{ message }}
fix: escape keys in generated types#143
Merged
Merged
Conversation
negative lookahead to check number at key[0]
Contributor
Author
pi0
changed the title
pi0
approved these changes
Dec 16, 2024
pi0
left a comment
pi0
left a comment
Member
There was a problem hiding this comment.
Thanks for PR and tests ❤️
I've refactored to use knitwork utils which is little bit safer
pi0
changed the title
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
2 participants
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.
escapeKeyfunction was not checking for valid property names. For example,{ "2ndKey" : "…" }was returning2ndKey: stringcausing ts errors.I originally encountered this error opening
.nuxt/types/schema.d.tscontaining tailwind config with2xl,3xl...Hope this pull request help.