-
Notifications
You must be signed in to change notification settings - Fork 3
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
feat(dumping): support lineWidth #24
Conversation
package.json
Outdated
"lodash": "^4.17.15", | ||
"yaml-ast-parser": "~0.0.43" | ||
"yaml-ast-parser": "stoplightio/yaml-ast-parser#ba8043e2eb7b444789a424754935f991572c25a1" |
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.
uh... shouldn't we publish it?
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.
@marbemac thoughts?
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.
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.
Approved, just need to update to use https://www.npmjs.com/package/@stoplight/yaml-ast-parser?activeTab=versions.
…#25) * fix: do not report duplicate keys errors for keys added by merge keys * test: extra override scenario
🎉 This PR is included in version 3.2.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Will 'fix' https://github.com/stoplightio/studio/issues/68.
To me, the above is not really an issue.
If we make this change, others might start complaining about the need of supporting folded block scalar style.
That said, it's still useful to have
lineWidth
working. I had to make a fork though, yet will try to make a PR out of it to make it land on upstream.