Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure strings that may be confused as YAML1.2 numbers are quoted #628

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

adammw
Copy link

@adammw adammw commented May 10, 2023

Ensure strings that may be confused as YAML1.2 numbers are quoted.

Example: 0o123 or 1e3 strings in Ruby will be printed without quotation marks, resulting in them changing to numbers in a YAML1.2-parser (like that used in Go).

Fixes #627

@djhoese
Copy link

djhoese commented Oct 9, 2024

@adammw Any chance you have time to continue working on this? I've run into this same problem where strings (git commit SHAs) that look like scientific notation are dumped with no quotes around them.

@adammw
Copy link
Author

adammw commented Dec 5, 2024

@djhoese Ironically that's the exact reason I started looking into this 😅 but also why it's been pretty low priority, the "solution" is just to rewrite the commit to get a different SHA so it doesn't hit this condition

@adammw adammw force-pushed the adammw/yaml12-number branch from 5279e18 to 21eb63f Compare December 5, 2024 06:14
@adammw adammw force-pushed the adammw/yaml12-number branch from 21eb63f to cce65cc Compare December 5, 2024 06:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

YAML string in exponential format cannot be loaded by YAML 1.2 parser
3 participants