* @deprecated Use {@link #FileSource(Path)} instead.
     */
    @Deprecated
    public FileSource(File file) {
        this(Objects.requireNonNull(file, "file cannot be null").toPath());
    }

    /**
     * Creates a new source backed by the specified file.
     *
     * @param path The file, must not be {@code null}.
     * @since 4.0.0
     */
    public FileSource(Path path) {

import okio.ForwardingSink
import okio.Path
import okio.Sink

class FaultyFileSystem constructor(
  delegate: FileSystem?,
) : ForwardingFileSystem(delegate!!) {
  private val writeFaults: MutableSet<Path> = LinkedHashSet()
  private val deleteFaults: MutableSet<Path> = LinkedHashSet()
  private val renameFaults: MutableSet<Path> = LinkedHashSet()

  fun setFaultyWrite(
    file: Path,
    faulty: Boolean,
  ) {

Todo el mismo proceso que se aplica para los parámetros de path también se aplica para los parámetros de query:

* Soporte del editor (obviamente)
* <abbr title="convirtiendo el string que viene de un request HTTP en datos de Python">"Parsing"</abbr> de datos
* Validación de datos
* Documentación automática

## Valores por defecto

Como los parámetros de query no son una parte fija de un path, pueden ser opcionales y pueden tener valores por defecto.

# Body - Multiple Parameters { #body-multiple-parameters }

Now that we have seen how to use `Path` and `Query`, let's see more advanced uses of request body declarations.

## Mix `Path`, `Query` and body parameters { #mix-path-query-and-body-parameters }

First, of course, you can mix `Path`, `Query` and request body parameter declarations freely and **FastAPI** will know what to do.

    super.delete(path, mustExist)
  }

  override fun sink(
    path: Path,
    mustCreate: Boolean,
  ): Sink {
    log("sink($path)")

    return super.sink(path, mustCreate)
  }

  override fun source(file: Path): Source {
    log("source($file)")

    return super.source(file)
  }

                        final Path path = ResourceUtil.getViewTemplatePath(names);
                        Files.createDirectories(path.getParent());
                        Files.copy(zis, path, StandardCopyOption.REPLACE_EXISTING);
                    } else if ("css".equals(names[0])) {
                        names[0] = themeName;
                        final Path path = ResourceUtil.getCssPath(names);

# Çerez (Cookie) Parametreleri

`Query` (Sorgu) ve `Path` (Yol) parametrelerini tanımladığınız şekilde çerez parametreleri tanımlayabilirsiniz.

## Import `Cookie`

Öncelikle, `Cookie`'yi projenize dahil edin:

{* ../../docs_src/cookie_params/tutorial001_an_py310.py hl[3] *}

## `Cookie` Parametrelerini Tanımlayın

Çerez parametrelerini `Path` veya `Query` tanımlaması yapar gibi tanımlayın.

     *
     * @return the current working directory path, or null if not set
     */
    @Nullable
    Path cwd();

    /**
     * Returns the Maven home directory.
     * If not explicitly set, this value will be detected during parsing.
     *
     * @return the Maven home directory path, or null if not set
     */
    @Nullable
    Path mavenHome();

    /**

Y todas estas miles de *path operations* pueden ser tan pequeñas como 3 líneas:

{* ../../docs_src/security/tutorial002_an_py310.py hl[30:32] *}

## Resumen

Ahora puedes obtener el usuario actual directamente en tu *path operation function*.

Ya estamos a mitad de camino.

Solo necesitamos agregar una *path operation* para que el usuario/cliente envíe realmente el `username` y `password`.

    /**
     * Create new handle information
     * @param path the file path
     * @param guid the create GUID
     * @param fileId the 16-byte file ID
     * @param type the handle type
     * @param timeout the timeout in milliseconds
     * @param leaseKey the associated lease key (can be null)
     */
    public HandleInfo(String path, HandleGuid guid, byte[] fileId, HandleType type, long timeout, Smb2LeaseKey leaseKey) {