-
Notifications
You must be signed in to change notification settings - Fork 6
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
Fix yaml parsing #110
Fix yaml parsing #110
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe you still need to migrate the code in resourceName
and getHeader
away from String()
.
Please update your testdata to include some yaml tags, to verify correct handling.
e3310f2
to
c9f0ce4
Compare
new cilium example (cherry picked from commit 6b52469)
c9f0ce4
to
f29ebda
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This is a stacked PR on top of #107 (the last 3 commits are the new additions) that modifies how we interact with yaml strings in our AST parsing. Instead of using the
String()
method on nodes, which requires mutating the nodes to handle comments properly, this PR updates our codebase to use theValue
method of the ast nodes instead. This gives us better output with correct formatting, eg. correct handling of octal values of file permissions and better multiline string formatting.Fixes: #109
Fixes #112
Fixes: #115