8000 Comparing v0.16.0...v0.17.0 · google/yamlfmt · GitHub
[go: up one dir, main page]

Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: google/yamlfmt
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v0.16.0
Choose a base ref
...
head repository: google/yamlfmt
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v0.17.0
Choose a head ref
  • 5 commits
  • 107 files changed
  • 1 contributor

Commits on May 17, 2025

  1. Configuration menu
    Copy the full SHA
    fe23d5e View commit details
    Browse the repository at this point in the history

Commits on May 18, 2025

  1. 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
    braydonk authored May 18, 2025
    Configuration menu
    Copy the full SHA
    9e812c9 View commit details
    Browse the repository at this point in the history
  2. 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
    braydonk authored May 18, 2025
    Configuration menu
    Copy the full SHA
    bb1d122 View commit details
    Browse the repository at this point in the history
  3. 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
    braydonk authored May 18, 2025
    Configuration menu
    Copy the full SHA
    ea03c83 View commit details
    Browse the repository at this point in the history

Commits on May 25, 2025

  1. 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
    braydonk authored May 25, 2025
    Configuration menu
    Copy the full SHA
    45e5cb5 View commit details
    Browse the repository at this point in the history
Loading
0