Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Native version fails to format record patterns in switches if the first nested pattern is final

Open
  • Is something wrong?
#1,257 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
tooling

Research direction

Reproduce the native formatter failure with the switch-pattern example in the issue, then compare it with the JVM formatter and the accepted variants. Done means the native version formats the failing record pattern consistently with the JVM version without regressing the other examples.

Written by the indexing model from the issue text.

Description

The following code fails to format when using the native version of the formatter. (The JVM version works fine.)

class Main {
    void test() {
        switch (test) {
            case Test(final var x, final var y) -> {}
        }
    }
}

On the other hand, both of these examples are accepted:

class Main {
    void test() {
        switch (test) {
            case Test(var x, final var y) -> {}
        }
    }
}

class Main {
    void test() {
        if (test instanceof Test(final var x, final var y)) {}
    }
}

Tested on version 1.27.0.

Dominant language
Java
Stars
6.2k
Forks
936
Avg merge
6m
Merged PRs (30d)
3

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from google/google-java-format

All issues in google/google-java-format

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.