assertTrue(builder instanceof MatchPhrasePrefixQueryBuilder);

        MatchPhrasePrefixQueryBuilder mpqb = (MatchPhrasePrefixQueryBuilder) builder;
        assertEquals("test", mpqb.value()); // Should be lowercase
    }

    @Test
    public void test_convertPrefixQuery_withUppercasePrefix_lowercaseDisabled() throws Exception {
        queryCommand.setLowercaseWildcard(false);

import java.util.HashSet;
import java.util.Set;
import java.util.regex.Matcher;
import java.util.regex.Pattern;
import java.util.stream.Stream;

/**
 * Generates Javadocs in a particular way.
 *
 * TODO: We should remove the workarounds here and migrate some of the changes here into the Javadoc task proper.
 */
public abstract class GradleJavadocsPlugin implements Plugin<Project> {

    @Inject

        // Set a test time using reflection
        long testTime = System.currentTimeMillis();
        setFieldValue(response, "lastWriteTime", testTime);

        // All time methods should return the same converted time
        long expectedTime = testTime + serverTimeZoneOffset;
        assertEquals(expectedTime, response.getCreateTime());
        assertEquals(expectedTime, response.getLastWriteTime());

            if it should exclude from the output the fields that had the same default
            value, even when they were explicitly set.
            """
        ),
    ] = False,
    exclude_none: Annotated[
        bool,
        Doc(
            """
            Pydantic's `exclude_none` parameter, passed to Pydantic models to define

            assertArrayEquals(new byte[] { 1, 2, 3 }, ctx.getSigningKey(), "signing key");
            assertTrue(ctx.isEstablished(), "should be established");

            byte[] in = new byte[] { 9, 8, 7, 6 };
            assertArrayEquals(new byte[] { 8, 7 }, ctx.initSecContext(in, 1, 2), "slice should match");

            assertEquals("NBHOST", ctx.getNetbiosName(), "NetBIOS name");

are working on. And as mentioned above, API changes should be discussed
thoroughly before moving to code.

Some examples of types of pull requests that are immediately helpful:

  - Fixing a bug without changing a public API.
  - Fixing or improving documentation.
  - Improvements to Maven configuration.

Guidelines for any code contributions:

1.  Any significant changes should be accompanied by tests. The project already

     *
     * @param tc
     *            context to use
     * @param authorityServerName
     *            The hostname of the server that should be queried. For maximum efficiency this should be the hostname
     *            of a domain controller however a member server will work as well and a domain controller may not

        assertFalse("Technical email should not contain @@", technicalEmail.contains("@@"));
        assertFalse("Support email should not contain @@", supportEmail.contains("@@"));

        // Verify correct email format
        assertEquals("******@****.***", technicalEmail);
        assertEquals("******@****.***", supportEmail);

        // Count @ occurrences - should be exactly 1

 * subscribers should be reasonably quick. If an event may trigger an extended process (such as a
 * database load), spawn a thread or queue it for later. (For a convenient way to do this, use an
 * {@link AsyncEventBus}.)
 *
 * <h2>Subscriber Methods</h2>
 *
 * <p>Event subscriber methods must accept only one argument: the event.
 *

            return false
        }
        /* js snippets almost always should be marked with `// CONSOLE`. js
         * snippets that shouldn't be marked `// CONSOLE`, like examples for
         * js client, should always be marked with `// NOTCONSOLE`.
         *
         * `sh` snippets that contain `curl` almost always should be marked
         * with `// CONSOLE`. In the exceptionally rare cases where they are