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
dumping is formating custom type wrong #576
Comments
Those string representations are equivalent: console.log(yaml.load(`
a: !<!mapInfo> '1'
b: !mapInfo '1'
`, { schema }))
// prints { a: Test { id: '1' }, b: Test { id: '1' } }
Does it cause any issues (e.g. interoperability with other parsers)? |
Yes they are equivalent but the same library throw an error when convert from |
+1 I am also working on a library where I want to be able to load yaml with custom tags, process/transform the data, and then dump the transformed data as yaml while preserving the original -- I want to be able to perform a diff and don't want every custom tag rewritten. If we had an option available when creating a Type (for example, a boolean flag -- Would you accept a PR for this? |
The text was updated successfully, but these errors were encountered: