* オプショナルのクエリパラメータ`limit`は`int`で、デフォルトは`100`です。

そして、これらの値を含む`dict`を返します。

### `Depends`のインポート

{* ../../docs_src/dependencies/tutorial001.py hl[3] *}

### "dependant"での依存関係の宣言

*path operation関数*のパラメータに`Body`や`Query`などを使用するのと同じように、新しいパラメータに`Depends`を使用することができます:

{* ../../docs_src/dependencies/tutorial001.py hl[13,18] *}

関数のパラメータに`Depends`を使用するのは`Body`や`Query`などと同じですが、`Depends`の動作は少し異なります。

`Depends`は１つのパラメータしか与えられません。

    fun asName(): String

    fun channel(): String
}

data class PerformanceTestPartialTrigger(
    val triggerName: String,
    val triggerId: String,
    val dependencies: List<PerformanceTestCoverage>,
)

data class PerformanceTestCoverage(
    private val uuid: Int,
    override val type: PerformanceTestType,
    override val os: Os,
    override val arch: Arch = Arch.AMD64,

  <properties>
    <!-- in: DefaultModelValidator, DefaultModelBuilder -->
    <checkstyle.violation.ignore>FileLength</checkstyle.violation.ignore>
  </properties>

  <dependencies>
    <dependency>
      <groupId>org.apache.maven</groupId>
      <artifactId>maven-api-annotations</artifactId>
    </dependency>
    <dependency>
      <groupId>org.apache.maven</groupId>

                ArtifactFactory artifactFactory,
                Set<Artifact> dependencies,
                String inheritedScope,
                ArtifactFilter dependencyFilter)
                throws InvalidVersionSpecificationException {
            Set<Artifact> projectArtifacts = new HashSet<>();

            for (Artifact d : dependencies) {
                VersionRange versionRange;

        name = flakyTestQuarantineProject.name + " (Trigger)"
        type = Type.COMPOSITE

        applyDefaultSettings()

        dependencies {
            snapshotDependencies(
                flakyTestQuarantineProject.buildTypes.map {
                    it as BaseGradleBuildType
                },
            )
        }
    })

register_toolchains("@rules_ml_toolchain//cc:linux_aarch64_linux_aarch64")

register_toolchains("@rules_ml_toolchain//cc:linux_aarch64_linux_aarch64_cuda")

# Initialize the TensorFlow repository and all dependencies.
#
# The cascade of load() statements and tf_workspace?() calls works around the
# restriction that load() statements need to be at the top of .bzl files.

  define for each {{{../../api/maven-api-model/maven.html#class_dependency}dependency type}} information on the artifact
  (classifier, extension, language) and how to manage it as dependency (add to classpath, include dependencies).

  They are replaced in Maven 4 with Maven 4 API Core's {{{../../api/maven-api-core/apidocs/org/apache/maven/api/Type.html}Dependency Types}},

            **/smoke-tests/build/reports/tests/** => post-smoke-tests
            **/build/version-info.properties => version-info.properties
            """.trimIndent(),
        )

        dependencies {
            snapshot(RelativeId("Check_Stage_${******@****.***rName}_Trigger")) {
                synchronizeRevisions = false
                onDependencyFailure = FailureAction.FAIL_TO_START

### Dependências { #dependencies }

O mesmo se aplica para as [dependências](tutorial/dependencies/index.md){.internal-link target=_blank}. Se uma dependência tem as funções com padrão `def` ao invés de `async def`, ela é rodada no threadpool externo.

### Sub-dependências { #sub-dependencies }

        }
        return getBasedir().resolve(dir);
    }

    /**
     * {@return the project direct dependencies (directly specified or inherited)}.
     */
    @Nonnull
    List<DependencyCoordinates> getDependencies();

    /**
     * {@return the project managed dependencies (directly specified or inherited)}.
     */
    @Nonnull
    List<DependencyCoordinates> getManagedDependencies();