-
Notifications
You must be signed in to change notification settings - Fork 78
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
*
string gets rendered with a bang on front
#113
Comments
Pleasure to read the ticket :) This one seems pretty easy: just add |
Hi @snoyberg, Impressed by how quickly you addressed this, yup the commit seems does the trick, thank you very much sir. Closing now. |
Thanks for confirming, new version released.
…On Sun, Jul 16, 2017 at 2:32 AM, Roman Gonzalez ***@***.***> wrote:
Hi @snoyberg <https://github.com/snoyberg>,
Impressed by how quickly you addressed this, yup the commit seems does the
trick, thank you very much sir.
Closing now.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#113 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AADBB5Y0F0w4p3hQ0Lyc8btLZHL0AZn7ks5sOUwkgaJpZM4OXmfK>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey Michael,
First of all, thank you for taking the time to read this ticket. I've been using your library to parse YAML files that I want to modify and re-render. I discovered this behavior when doing some template transformations:
I'm having some templates that have the value
'*'
in their fields, and when doing a parsing -> rendering it adds that bang at the beginning of the string. I'm guessing this behavior doesn't come from this library but from the libYAML one. Is there a way to stop this behavior?The text was updated successfully, but these errors were encountered: