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

Switch to gopkg.in/yaml.v3 #163

Merged
merged 1 commit into from
Feb 3, 2024
Merged

Conversation

elboulangero
Copy link
Contributor

The main reason to switch (apart from keeping dependencies up-to-date) is the default behaviour for line wrapping. In yaml.v2, the default was line wrapping after 80 characters. In yaml.v3, no line wrapping by default.

For mirrorbits, line wrapping manifests itself in the show and edit commands. It's an issue, in the sense that it makes it difficult for scripts to interact with those commands, since long values might spread over several lines. For example, parsing the output of mirrorbits show with grep is error prone because of line wrapping.

This commit bumps the build depencency gopkg.in/yaml from v2 to v3, thus disabling line wrapping in yaml output.

Closes: #153

The main reason to switch (apart from keeping dependencies up-to-date)
is the default behaviour for line wrapping. In yaml.v2, the default was
line wrapping after 80 characters. In yaml.v3, no line wrapping by
default.

For mirrorbits, line wrapping manifests itself in the `show` and `edit`
commands. It's an issue, in the sense that it makes it difficult for
scripts to interact with those commands, since long values might spread
over several lines. For example, parsing the output of `mirrorbits show`
with `grep` is error prone because of line wrapping.

This commit bumps the build depencency gopkg.in/yaml from v2 to v3, thus
disabling line wrapping in yaml output.

Closes: etix#153
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Line-wrapping in YAML output makes life difficult
2 participants