This repository was archived by the owner on Dec 16, 2025. It is now read-only.
Use double quotes for JSON object keys#612
Merged
MarkDaoust merged 1 commit intogoogle-gemini:mainfrom Oct 29, 2024
Merged
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 of the change
Use double-quoted string instead of single-quoted string in JSON.
Motivation
The string 'code_execution' is unexpectedly single-quoted in a JSON string when it should be double-quoted. Apparently this still works for the API (as does not quoting the object key at all) but the Bash syntax highligher is confused and thinks that the 'code_execution' text is not part of the string.
Type of change
Choose one: Documentation
Checklist
git pull --rebase upstream main).