Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/google/google-java-format/compare/v1.23.0...v1.24.0 below:

Comparing v1.23.0...v1.24.0 · google/google-java-format · GitHub

• Pricing

Failed to load repositories. Confirm that selected base ref is valid, then try again.

Loading

Failed to load repositories. Confirm that selected head ref is valid, then try again.

Loading

• 14 commits
• 26 files changed
• 8 contributors

1. Configuration menu Browse the repository at this point in the history

1. Avoid mangling {@snippet ...}.

   This CL also implements some minimal formatting behavior _around_ `{@snippet ...}` (namely, a blank line before and after). It does not make any effort to change formatting _inside_ `{@snippet ...}`, only to stop reflowing it blindly.
   
   PiperOrigin-RevId: 665555661

   cpovirk

   authored and

   google-java-format Team

   committed

   Aug 20, 2024 Configuration menu Browse the repository at this point in the history

1. Configuration menu Browse the repository at this point in the history
2. Configuration menu Browse the repository at this point in the history
3. Configuration menu Browse the repository at this point in the history
4. Configuration menu Browse the repository at this point in the history

1. Configuration menu Browse the repository at this point in the history

1. Fix package version metadata #9.

   * ebnf-mode: Last change 13 years ago with open PR from phst from 2019.  For the sake of the current package version metadata work, just slap in a pkg.el file for now.
   * llm-goose: Missing header.
   * gyp: Missing header.
   * lv: Include pkg.el added earlier.
   
   PiperOrigin-RevId: 667696660

   Configuration menu Browse the repository at this point in the history

1. Configuration menu Browse the repository at this point in the history

1. Configuration menu Browse the repository at this point in the history

2. Always run integration test for #1161

   The intent was to only run the test on JDK 23+ and to disable it until the linked issue was fixed, but it actually resulted in the test being discovered and run on all JDK versions.
   
   That's fine, because the test is backwards compatible (`///` comments are valid in all versions, they just aren't markdown comments until 23).
   
   The test is being fixed in #1161
   
   PiperOrigin-RevId: 674352956

   cushon

   authored and

   google-java-format Team

   committed

   Sep 13, 2024 Configuration menu Browse the repository at this point in the history

1. Configuration menu Browse the repository at this point in the history

1. Fix column numbers in diagnostics

   Despite documentation to the contrary, the column numbers are already 1-indexed. The comment was added in unknown commit when g-j-f was still implemented using ecj instead of javac, so maybe it was true then?
   
   PiperOrigin-RevId: 681451766

   cushon

   authored and

   google-java-format Team

   committed

   Oct 2, 2024 Configuration menu Browse the repository at this point in the history

1. Configuration menu Browse the repository at this point in the history

Loading

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 v1.23.0...v1.24.0

You can’t perform that action at this time.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4