Update vobject-js output properties to ensure that the maximum line length of output properties doesn't exceed 75 characters in length. #24
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This patch is meant to address a minor issue in the output format of rendered vobjects.
Each line that is long enough would end up being split to ensure that the content itself was never longer than 75 characters. Every line, after the first would be joined with the string '\r\n ' in order to ensure correct line endings and a continuation. This means that wrapped lines would end up being 76 characters in length instead of the 75 intended.
In addition to the aforementioned change, this also updates packages as specified by the test process to ensure they are up-to-date and pass the security checks.
As a result, the patch for the semantic version has also been updated.