* `"function"`: iniciar la dependencia antes de la *path operation function* que maneja el request, terminar la dependencia después de que termine la *path operation function*, pero **antes** de que el response se envíe de vuelta al cliente. Entonces, la función de dependencia se ejecutará **alrededor** de la *path operation **function***.

		config.HelpKV{
			Key:         target.KafkaClientTLSCert,
			Description: "path to client certificate for mTLS auth",
			Optional:    true,
			Type:        "path",
			Sensitive:   true,
		},
		config.HelpKV{
			Key:         target.KafkaClientTLSKey,
			Description: "path to client key for mTLS auth",
			Optional:    true,
			Type:        "path",
			Sensitive:   true,
		},
		config.HelpKV{

        assertTrue(file.getPath().endsWith("/shared/path/file.txt"), "Path should end correctly");
        assertEquals("shared", file.getShare(), "Share should be extracted correctly");
        assertNotNull(file.getParent(), "Parent should not be null");
        assertTrue(file.getParent().endsWith("/shared/path/"), "Parent path should be correct");
    }

    @Test
    void testUNCPath() throws Exception {

        return this.userDisplayName;
    }

    /**
     * Returns the path to the user's logon script.
     * @return the logon script path
     */
    public String getLogonScript() {
        return this.logonScript;
    }

    /**
     * Returns the path to the user's profile.
     * @return the profile path
     */
    public String getProfilePath() {
        return this.profilePath;
    }

This doesn't go inside of each JSON Schema contained in OpenAPI, this goes outside, in the *path operation* directly.

### Using the `openapi_examples` Parameter { #using-the-openapi-examples-parameter }

You can declare the OpenAPI-specific `examples` in FastAPI with the parameter `openapi_examples` for:

* `Path()`
* `Query()`
* `Header()`
* `Cookie()`
* `Body()`
* `Form()`
* `File()`

In those cases, you can use the *path operation decorator* parameter `response_model` instead of the return type.

You can use the `response_model` parameter in any of the *path operations*:

* `@app.get()`
* `@app.post()`
* `@app.put()`
* `@app.delete()`
* etc.

     * Builds the effective settings of the specified settings paths.
     *
     * @return the result of the settings building, never {@code null}
     * @throws SettingsBuilderException if the effective settings could not be built
     */
    @Nonnull
    default SettingsBuilderResult build(
            @Nonnull Session session, @Nonnull Path installationSettingsPath, @Nonnull Path userSettingsPath) {

    - 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: |

 * specific language governing permissions and limitations
 * under the License.
 */
package org.apache.maven.cling.invoker.mvnup.goals;

import java.nio.file.Path;
import java.nio.file.Paths;
import java.util.Map;
import java.util.Optional;

import eu.maveniverse.domtrip.Document;
import eu.maveniverse.domtrip.Editor;
import eu.maveniverse.domtrip.Element;

            </ul>

            <p>If this property is specified but is a relative path,
            then the path is resolved against the above-cited default value.</p>

            <p>When a target path is explicitly specified, the values of the {@code module} and {@code targetVersion}
            elements are not used for inferring the path (they are still used as compiler options however).