have prod supersource, even if they have none. GWT is happy to ignore us
    when we specify a nonexistent path.

    (I hope that this workaround does not cause its own problems in the future.)
-->
<super-source path="super"/>

<inherits name="com.google.common.annotations.Annotations" />
<inherits name="com.google.common.base.Base" />
<inherits name="com.google.gwt.core.Core" />

    have prod supersource, even if they have none. GWT is happy to ignore us
    when we specify a nonexistent path.

    (I hope that this workaround does not cause its own problems in the future.)
-->
<super-source path="super"/>

<inherits name="com.google.common.annotations.Annotations" />
<inherits name="com.google.common.base.Base" />

    have prod supersource, even if they have none. GWT is happy to ignore us
    when we specify a nonexistent path.

    (I hope that this workaround does not cause its own problems in the future.)
-->
<super-source path="super"/>

<inherits name="com.google.common.annotations.Annotations" />
<inherits name="com.google.common.base.Base" />

     * Test writeBytesWireFormat.
     */
    @Test
    void testWriteBytesWireFormat() {
        // Assuming path is ASCII and does not use unicode
        String dirName = "\testDir";
        SmbComDeleteDirectory sdd = new SmbComDeleteDirectory(dirName);
        sdd.useUnicode = false;
        // format byte + path + null terminator
        byte[] expected = new byte[1 + dirName.length() + 1];
        expected[0] = 0x04; // buffer format

 *
 * @since 4.0.0
 */
@Experimental
public interface RepositoryFactory extends Service {

    @Nonnull
    LocalRepository createLocal(@Nonnull Path path);

    @Nonnull
    RemoteRepository createRemote(@Nonnull String id, @Nonnull String url);

    @Nonnull
    RemoteRepository createRemote(@Nonnull Repository repository);

    @Nonnull

                return Optional.of(msgs[i]);
            }
        }
        return Optional.empty();
    }

    // Producer for code->message pairs covering all known constants (happy path)
    static Stream<Arguments> knownCodeMessagePairs() {
        return Stream.of(Arguments.of(WinError.ERROR_SUCCESS, "The operation completed successfully."),

## Usa la dependencia

Entonces podemos usar la dependencia con:

{* ../../docs_src/dependencies/tutorial005_an_py310.py hl[23] *}

/// info | Información

Fíjate que solo estamos declarando una dependencia en la *path operation function*, `query_or_cookie_extractor`.

Pero **FastAPI** sabrá que tiene que resolver `query_extractor` primero, para pasar los resultados de eso a `query_or_cookie_extractor` al llamarlo.

///

```mermaid

También puedes usar `url_for()` dentro de la plantilla, toma como argumentos los mismos que usaría tu *path operation function*.

Entonces, la sección con:

{% raw %}

```jinja
<a href="{{ url_for('read_item', id=id) }}">
```

{% endraw %}

...generará un enlace hacia la misma URL que manejaría la *path operation function* `read_item(id=id)`.

Por ejemplo, con un ID de `42`, esto se renderizaría como:

    - uses: actions/cache@v4
      with:
        path: ~/.m2/repository
        key: ${{ runner.os }}-maven-${{ hashFiles('**/pom.xml') }}
        restore-keys: |
          ${{ runner.os }}-maven-
    - name: Checkout fess-parent
      uses: actions/checkout@v4
      with:
        repository: codelibs/fess-parent
        ref: ${{ env.PARENT_BRANCH }}
        path: fess-parent
    - name: Install fess-parent
      run: |

            <p><b>Default value is</b>: parent value [+ path adjustment] + (artifactId or project.directory property), or just parent value if
            project's {@code child.project.url.inherit.append.path="false"}</p>
            ]]>
          </description>
          <type>String</type>
        </field>
        <field xml.attribute="true" xml.tagName="child.project.url.inherit.append.path">
          <name>childProjectUrlInheritAppendPath</name>