@Resource
    private UserService userService;

    /**
     * Retrieves user settings with pagination.
     *
     * @param body the search parameters for filtering and pagination
     * @return JSON response containing user settings list
     */
    // GET /api/admin/user/settings
    // PUT /api/admin/user/settings
    @Execute
    public JsonResponse<ApiResult> settings(final SearchBody body) {

# Потоковая передача данных { #stream-data }

Если вам нужно передавать потоковые данные, которые можно представить как JSON, воспользуйтесь [стримингом JSON Lines](../tutorial/stream-json-lines.md).

Но если вы хотите передавать в потоке чистые бинарные данные или строки, ниже показано, как это сделать.

/// info | Информация

Добавлено в FastAPI 0.134.0.

///

## Варианты использования { #use-cases }

<span style="color: green;">[INFO]</span> Start watching changes
<span style="color: green;">[INFO]</span> Start detecting changes
```

And even more text

```json
{
    // This is a sample JSON code block
    "greeting": "Hello, world!" // Greeting
}
```

Диаграма Mermaid

```mermaid
flowchart LR
    stone(philosophers-stone) -->|requires| harry-1[harry v1]

<span style="color: green;">[INFO]</span> Start watching changes
<span style="color: green;">[INFO]</span> Start detecting changes
```

And even more text

```json
{
    // This is a sample JSON code block
    "greeting": "Hello, world!" // Greeting
}
```

Диаграма Mermaid

```mermaid
flowchart LR
    stone(philosophers-stone) -->|requires| harry-1[harry v1]

import (
	"encoding/xml"
	"unicode/utf8"
)

// Tag - a tag for a replication configuration Rule filter.
type Tag struct {
	XMLName xml.Name `xml:"Tag" json:"Tag"`
	Key     string   `xml:"Key,omitempty" json:"Key,omitempty"`
	Value   string   `xml:"Value,omitempty" json:"Value,omitempty"`
}

var (
	errInvalidTagKey   = Errorf("The TagKey you have provided is invalid")

///

## Paramètres multiples du corps de la requête { #multiple-body-parameters }

Dans l'exemple précédent, les chemins d'accès attendraient un corps de la requête JSON avec les attributs d'un `Item`, par exemple :

```JSON
{
    "name": "Foo",
    "description": "The pretender",
    "price": 42.0,
    "tax": 3.2
}
```

		// U+2029 is PARAGRAPH SEPARATOR.
		// They are both technically valid characters in JSON strings,
		// but don't work in JSONP, which has to be evaluated as JavaScript,
		// and can lead to security holes there. It is valid JSON to
		// escape them, so we do so unconditionally.
		// See http://timelessrepo.com/json-isnt-a-javascript-subset for discussion.
		if c == '\u2028' || c == '\u2029' {
			if start < i {

type batchJobInfo struct {
	mu sync.RWMutex `json:"-" msg:"-"`

	Version       int       `json:"-" msg:"v"`
	JobID         string    `json:"jobID" msg:"jid"`
	JobType       string    `json:"jobType" msg:"jt"`
	StartTime     time.Time `json:"startTime" msg:"st"`
	LastUpdate    time.Time `json:"lastUpdate" msg:"lu"`
	RetryAttempts int       `json:"retryAttempts" msg:"ra"`
	Attempts      int       `json:"attempts" msg:"at"`

        assertNotNull(result);
        assertTrue(result instanceof MatchAllQueryBuilder);

        // Verify the query builder generates correct JSON
        String json = result.toString().replaceAll("[\\s\\n]", "");
        assertEquals("{\"match_all\":{\"boost\":1.0}}", json);
    }

    @Test
    public void test_execute_withDifferentBoost() {
        // Test execute method with different boost value

예를 들면, 위의 이 모델은 JSON "`object`" (혹은 파이썬 `dict`)을 다음과 같이 선언합니다:

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

...`description`과 `tax`는 (기본 값이 `None`으로 되어 있어) 선택적이기 때문에, 이 JSON "`object`"는 다음과 같은 상황에서도 유효합니다:

```JSON
{
    "name": "Foo",
    "price": 45.2
}
```