"summary": "Read Root",
                        "operationId": "read_root__get",
                        "responses": {
                            "200": {
                                "description": "Successful Response",
                                "content": {
                                    "application/json": {
                                        "schema": {

    workspace: /dev/shm/elastic+elasticsearch+%BRANCH%+multijob+third-party-tests-s3
    display-name: "elastic / elasticsearch # %BRANCH% - third party tests s3"
    description: "Testing of the Elasticsearch %BRANCH% third party tests against S3\n"
    builders:
      - inject:
          properties-file: '.ci/java-versions.properties'
          properties-content: |

---
- job:
    name: "elastic+elasticsearch+pull-request+bwc"
    display-name: "elastic / elasticsearch - pull request bwc"
    description: "Testing of Elasticsearch pull requests - bwc"
    workspace: "/dev/shm/elastic+elasticsearch+pull-request+bwc"
    scm:
      - git:
          refspec: "+refs/pull/${ghprbPullId}/*:refs/remotes/origin/pr/${ghprbPullId}/*"
          branches:
            - "${ghprbActualCommit}"
    triggers:

Par exemple, le modèle ci-dessus déclare un JSON « `object` » (ou `dict` Python) tel que :

```JSON
{
    "name": "Foo",
    "description": "An optional description",
    "price": 45.2,
    "tax": 3.5
}
```

... `description` et `tax` étant des attributs optionnels (avec `None` comme valeur par défaut), ce JSON « `object` » serait aussi valide :

```JSON
{
    "name": "Foo",

    <version>999.0.0-HEAD-android-SNAPSHOT</version>
  </parent>
  <artifactId>guava-tests</artifactId>
  <name>Guava Unit Tests</name>
  <description>
    The unit tests for the Guava libraries - separated into a
    separate artifact to allow for the testlibs to depend on guava
    itself.
  </description>
  <dependencies>
    <dependency>
      <groupId>${project.groupId}</groupId>
      <artifactId>guava-testlib</artifactId>

    /** The name of the file configuration (required, maximum 200 characters). */
    @Required
    @Size(max = 200)
    public String name;

    /** The description of the file configuration (maximum 1000 characters). */
    @Size(max = 1000)
    public String description;

    /** The file paths to crawl (required, must be valid file URIs). */
    @Required
    @UriType(protocolType = ProtocolType.FILE)

import org.junit.runners.JUnit4

actual class PublicSuffixTestRunner(
  klass: Class<*>,
) : Runner() {
  private val delegate = JUnit4(klass)

  override fun getDescription() = delegate.description

  override fun run(notifier: RunNotifier?) = delegate.run(notifier)

  override fun testCount() = delegate.testCount()
}

actual fun beforePublicSuffixTest() {

    public String createdTime;

    /** Search/filter parameter for data configuration version number. */
    public String versionNo;

    /** Search/filter parameter for data configuration description. */
    public String description;

    /**
     * Creates a new DataConfigPager with default values.
     * Initializes pagination settings and clears all search parameters.
     */
    public DataConfigPager() {

在这些场景中，常见的做法是发送 “JSON Lines”，这是一种每行发送一个 JSON 对象的格式。

响应的内容类型是 `application/jsonl`（而不是 `application/json`），响应体类似这样：

```json
{"name": "Plumbus", "description": "A multi-purpose household device."}
{"name": "Portal Gun", "description": "A portal opening device."}
{"name": "Meeseeks Box", "description": "A box that summons a Meeseeks."}
```

它与 JSON 数组（相当于 Python 的 list）非常相似，但不是用 `[]` 包裹、并在各项之间使用 `,` 分隔，而是每行一个 JSON 对象，彼此以换行符分隔。

/// info | 信息

plugins {
    id("gradlebuild.build-logic.kotlin-dsl-gradle-plugin")
    id("gradlebuild.build-logic.groovy-dsl-gradle-plugin")
}

description = "Provides plugins that create update tasks for the Gradle build"

dependencies {
    implementation(projects.jvm)
    implementation("gradlebuild:basics")
    implementation("gradlebuild:module-identity")
    implementation(buildLibs.gson)
    implementation(buildLibs.jsoup)