-
Notifications
You must be signed in to change notification settings - Fork 61
Comparing changes
Open a pull request
base repository: google/yamlfmt
base: v0.16.0
head repository: google/yamlfmt
compare: v0.17.2
- 9 commits
- 108 files changed
- 3 contributors
Commits on May 17, 2025
-
Configuration menu - View commit details
-
Copy full SHA for fe23d5e - Browse repository at this point
Copy the full SHA fe23d5eView commit details
Commits on May 18, 2025
-
Vendor github.com/braydonk/yaml (#245)
* Vendor github.com/braydonk/yaml The yaml.v3 package upstream is now archived. This means there is no hope of my patches ever being committed upstream. As such, there is nothing to gain by maintaining this library in a separate repo. It will be easier for people to contribute to if it's in this repo. I will keep github.com/braydonk/yaml alive purely for the select few who pull the package for the couple of patches that upstream never merged. * fix test workflows cause the yaml package fails everything
Configuration menu - View commit details
-
Copy full SHA for 9e812c9 - Browse repository at this point
Copy the full SHA 9e812c9View commit details -
pkg/yaml: correct alias keys (#247)
* pkg/yaml: correct alias keys As outlined in #247, the yaml library did not initially handle this edge case of using an alias node as a key properly. This PR adds functionality to correct that. In case there is some other edge case where this breaks, the `disable_alias_key_correction` formatter config option was added. * forgot to fix this comment * forgot to enable the setting for this test
Configuration menu - View commit details
-
Copy full SHA for bb1d122 - Browse repository at this point
Copy the full SHA bb1d122View commit details -
formatters/basic: add force_array_style (#248)
* formatters/basic: add force_array_style This PR adds the `force_array_style` feature to the basic formatter, which allows the user to force either `block` or `flow` sequence style in the formatted document. * add the license I forgot * remove TODO comment I left in * oops overwrote the test expectation * readded removed newline
Configuration menu - View commit details
-
Copy full SHA for ea03c83 - Browse repository at this point
Copy the full SHA ea03c83View commit details
Commits on May 25, 2025
-
Add options for seeing which files were formatted (#249)
* Add options for seeing which files were formatted This PR adds two features for keeping track of which files were edited by yamlfmt: `-verbose`, `-v`: When formatting with verbose mode on, the modified paths will be printed. `-debug diffs`: When formatting with `diffs` debug code, all formatting diffs will be printed. Additionally: * Fixed the `tempfile` bug that wouldn't replicate subdirectories properly * Added `-q` short version of the `-quiet` flag * fix integration tests
Configuration menu - View commit details
-
Copy full SHA for 45e5cb5 - Browse repository at this point
Copy the full SHA 45e5cb5View commit details
Commits on Jun 10, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 1aab10e - Browse repository at this point
Copy the full SHA 1aab10eView commit details
Commits on Jun 11, 2025
-
Configuration menu - View commit details
-
Copy full SHA for bad3941 - Browse repository at this point
Copy the full SHA bad3941View commit details
Commits on Jun 19, 2025
-
formatters/basic: fix just comments edge case (#259)
When `yaml.v3` parses a document that's just comments, it ends up parsing no actual nodes and thus loses the comment information. This will now be treated as an edge case and return the original content, in essence not modifying it if the yaml parsed successfully but no nodes are parsed out.
Configuration menu - View commit details
-
Copy full SHA for 1e2fd2c - Browse repository at this point
Copy the full SHA 1e2fd2cView commit details
Commits on Jun 23, 2025
-
Remove trailing whitespace from merge aliases. (#260)
* fix(yaml): Remove trailing whitespace from merge aliases. PR #247 introduced a regression with YAML documents such as this: ```yaml config: &shared key: value instance: <<: *shared ``` Due to the "correct alias keys" setting, a extra space was emitted after `*shared`. This created trailing whitespace which many tools (rightly) complain about. This change adds an extra condition to only emit the space in the "simple key" context. I'm not enough of a YAML expert to be sure this is the right thing to do, but it fixes my problem without failing any of the existing tests. * test(formattest): Print a diff between the expected and actual result.
Configuration menu - View commit details
-
Copy full SHA for 398e72a - Browse repository at this point
Copy the full SHA 398e72aView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v0.16.0...v0.17.2