Eine Response hätte einen Content-Type von `application/jsonl` (anstelle von `application/json`) und der Body sähe etwa so aus:

```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."}
```

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE components PUBLIC "-//DBFLUTE//DTD LastaDi 1.0//EN"
	"http://dbflute.org/meta/lastadi10.dtd">
<components namespace="fessCrawler">
	<include path="crawler/container.xml" />

	<component name="logHelper"
		class="org.codelibs.fess.helper.CrawlerLogHelper">
	</component>

package common

enum class FlakyTestStrategy {
    INCLUDE,
    EXCLUDE,
    ONLY,
    ;

    override fun toString() = name.lowercase()

{
    "name": "s3-zip-example",
    "version": "1.0.0",
    "main": "main.js",
    "dependencies": {
        "aws-sdk": "^2.924.0"
    }

     */
    public static final String PATH_SEPARATOR = System.getProperty("path.separator");

    /**
     * <code>os.name</code> system property. Example: <code>Mac OS X</code>
     */
    public static final String OS_NAME = System.getProperty("os.name");

    /**
     * <code>java.io.tmpdir</code> system property. Example: /tmp
     */

///

{* ../../docs_src/response_model/tutorial005_py310.py hl[29,35] *}

/// tip | Consejo

La sintaxis `{"name", "description"}` crea un `set` con esos dos valores.

Es equivalente a `set(["name", "description"])`.

///

#### Usar `list`s en lugar de `set`s { #using-lists-instead-of-sets }

	"http://dbflute.org/meta/lastadi10.dtd">
<components>
	<include path="convention.xml" />
	<include path="lastaflute.xml" />
	
	<!-- Register systemProperties for test environment -->
	<component name="systemProperties" class="org.codelibs.fess.unit.TestSystemProperties" />

	versionID := ""
	var uv uuid.UUID
	// check if the version is not "null"
	if j.VersionID != uv {
		versionID = uuid.UUID(j.VersionID).String()
	}
	fi := FileInfo{
		Volume:    volume,
		Name:      path,
		ModTime:   time.Unix(0, j.ModTime).UTC(),
		VersionID: versionID,
		Deleted:   true,
	}
	fi.Metadata = make(map[string]string, len(j.MetaSys))
	for k, v := range j.MetaSys {

                        "parameters": [
                            {
                                "required": True,
                                "schema": {"title": "Id", "type": "integer"},
                                "name": "id",
                                "in": "path",
                            }
                        ],
                        "responses": {
                            "204": {"description": "Successful Response"},

#### `HeroBase` - temel sınıf { #herobase-the-base-class }

Önce tüm modeller tarafından **paylaşılan alanları** içeren bir `HeroBase` modeliyle başlayalım:

* `name`
* `age`

{* ../../docs_src/sql_databases/tutorial002_an_py310.py ln[7:9] hl[7:9] *}

#### `Hero` - *table model* { #hero-the-table-model }