Repository navigation
docs[toKebabCaseKeys]: fix kebab-case example comment in Korean docs - #2136
Merged
Merged
Conversation
…of kebab-case The example comment for `toKebabCase` showed a `snake_case` result; fixed it to kebab-case.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
raon0211
approved these changes
Oct 8, 2026
This branch had an error being deployed
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.
Summary
The nested example in the Korean docs for
toKebabCaseKeysshowed snake_case keys in the result comment — the opposite of what the function does.Changes
docs/ko/reference/object/toKebabCaseKeys.mdto use kebab-case.