InvokerRequest invokerRequest =
                subject.parseInvocation(ParserRequest.mvn(Arrays.asList("-e", "-X"), mock(MessageBuilderFactory.class))
                        .cwd(Path.of(System.getProperty("userDir")))
                        .userHome(Path.of(System.getProperty("userHome")))
                        .build());

        Assertions.assertTrue(invokerRequest.options().isPresent());

concatenated in sorted order by pathname. Files in the directory matching the
glob "*stdlib/*minor" are treated specially. They should be in subdirectories
corresponding to standard library package paths, and headings for those package
paths will be generated automatically.

Files in this repo's `api/next` directory must have corresponding files in
`doc/next/*stdlib/*minor`.
The files should be in the subdirectory for the package with the new

 * referral level and target path for which DFS resolution is requested.
 *
 * @author mbechler
 */
public class DfsReferralRequestBuffer implements Encodable {

    private final int maxReferralLevel;
    private final String path;

    /**
     * Constructs a DFS referral request buffer
     *
     * @param filename the DFS path to request referral for

title: "x/pkgsite: package removal request for [type path here]"
labels: ["pkgsite/package-removal"]
body:
  - type: markdown
    attributes:
      value: "Please answer these questions before submitting your issue. Thanks!"
  - type: input
    id: package-path
    attributes:
      label: "What is the path of the package that you would like to have removed?"
      description: |

    }

    @Test
    @DisplayName("Should get path")
    void testGetPath() {
        // Given
        String path = "/test/path";
        when(mockReferralData.getPath()).thenReturn(path);

        // When
        String result = mockReferralData.getPath();

        // Then
        assertEquals(path, result);
        verify(mockReferralData).getPath();
    }

    @Test

///

## Оголошення атрибутів моделі { #declare-model-attributes }

Потім ви можете використовувати `Field` з атрибутами моделі:

{* ../../docs_src/body_fields/tutorial001_an_py310.py hl[11:14] *}

`Field` працює так само, як `Query`, `Path` і `Body`, має ті самі параметри тощо.

/// note | Технічні деталі

     * Downloads an object from storage.
     *
     * @param objectName the name/path of the object to download
     * @param outputStream the output stream to write data to
     */
    void downloadObject(String objectName, OutputStream outputStream);

    /**
     * Deletes an object from storage.
     *
     * @param objectName the name/path of the object to delete
     */
    void deleteObject(String objectName);

    /**

     * @param path the {@link Path}, must not be {@code null}
     * @throws ProjectBuilderException if the project cannot be created
     * @throws IllegalArgumentException if an argument is {@code null} or invalid
     * @see #build(ProjectBuilderRequest)
     */
    @Nonnull
    default ProjectBuilderResult build(@Nonnull Session session, @Nonnull Path path) throws ProjectBuilderException {

///

## Declare atributos do modelo { #declare-model-attributes }

Você pode então utilizar `Field` com atributos do modelo:

{* ../../docs_src/body_fields/tutorial001_an_py310.py hl[11:14] *}

`Field` funciona da mesma forma que `Query`, `Path` e `Body`, ele possui todos os mesmos parâmetros, etc.

/// note | Detalhes Técnicos

            "-Dorg.gradle.java.installations.auto-detect=false",
            "-Porg.gradle.java.installations.auto-detect=false",
            "\"-Dorg.gradle.java.installations.paths=$expectedInstallationPaths\"",
            "\"-Porg.gradle.java.installations.paths=$expectedInstallationPaths\"",
        ).joinToString(" ")
    }