errors.suffix = </li>
# ----------------------------------------------------------
# Javax Validator
# ---------------
constraints.AssertFalse.message = {item} harus bernilai false.
constraints.AssertTrue.message = {item} harus bernilai true.
constraints.DecimalMax.message = {item} harus kurang dari {value}.
constraints.DecimalMin.message = {item} harus lebih dari {value}.
constraints.Digits.message = {item} harus berupa angka. (expected: <number>.<number>)

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

/// info | 情報

以下も使用できます:

* `response_model_exclude_defaults=True`
* `response_model_exclude_none=True`

`exclude_defaults` と `exclude_none` については、[Pydanticのドキュメント](https://docs.pydantic.dev/1.10/usage/exporting_models/#modeldict)で説明されている通りです。

///

#### デフォルト値を持つフィールドに値があるデータ { #data-with-values-for-fields-with-defaults }

    simultaneously. This can be used to implement interactive conversations within a single HTTP
    call.

    Create duplex calls by overriding the new `RequestBody.isDuplex()` method to return true.
    This simple option dramatically changes the behavior of the request body and of the entire
    call.

    The `RequestBody.writeTo()` method may now retain a reference to the provided sink and

Тоді передайте параметр `deprecated=True` до `Query`:

{* ../../docs_src/query_params_str_validations/tutorial010_an_py310.py hl[19] *}

Документація буде показувати це таким чином:

<img src="/img/tutorial/query-params-str-validations/image01.png">

    }
  }

  public void testComposeOfFunctionsIsAssociative() {
    Map<Float, String> m = ImmutableMap.of(4.0f, "A", 3.0f, "B", 2.0f, "C", 1.0f, "D");
    Function<? super Integer, Boolean> h = Functions.constant(Boolean.TRUE);
    Function<? super String, Integer> g = new HashCodeFunction();
    Function<Float, String> f = Functions.forMap(m, "F");

    Function<Float, Boolean> c1 = Functions.compose(Functions.compose(h, g), f);

responsive) or $infix == \"\") {\n          @include generate-utility($utility, $infix, true);\n        }\n      }\n    }\n  }\n}\n\n\n// Print utilities\n@media print {\n  @each $key, $utility in $utilities {\n    // The utility can be disabled with `false`, thus check if the utility is a map first\n    // Then check if the utility needs print styles\n    @if type-of($utility) == \"map\" and map-get($utility, print) == true {\n      @include generate-utility($utility, \"-print\");\n    }\n  }\n}\n"]}...

Его нужно оставить на какое‑то время, так как клиенты его используют, но вы хотите, чтобы в документации он явно отображался как <dfn title="устаревший, не рекомендуется использовать">устаревший</dfn>.

Тогда передайте параметр `deprecated=True` в `Query`:

{* ../../docs_src/query_params_str_validations/tutorial010_an_py310.py hl[19] *}

В документации это будет показано так:

<img src="/img/tutorial/query-params-str-validations/image01.png">

## 棄用參數 { #deprecating-parameters }

現在假設你不再喜歡這個參數了。

你必須暫時保留它，因為還有用戶端在用，但你希望文件能清楚標示它是<dfn title="過時，不建議使用">已棄用</dfn>。

接著把參數 `deprecated=True` 傳給 `Query`：

{* ../../docs_src/query_params_str_validations/tutorial010_an_py310.py hl[19] *}

文件會這樣顯示：

<img src="/img/tutorial/query-params-str-validations/image01.png">

Bazı client’lar hâlâ kullandığı için bir süre tutmanız gerekiyor, ama dokümanların bunu açıkça <dfn title="kullanımdan kalkmış, kullanmamanız önerilir">deprecated</dfn> olarak göstermesini istiyorsunuz.

O zaman `Query`’ye `deprecated=True` parametresini geçin:

{* ../../docs_src/query_params_str_validations/tutorial010_an_py310.py hl[19] *}

Dokümanlarda şöyle görünür:

<img src="/img/tutorial/query-params-str-validations/image01.png">

Dann übergeben Sie den Parameter `deprecated=True` an `Query`:

{* ../../docs_src/query_params_str_validations/tutorial010_an_py310.py hl[19] *}

Die Dokumentation wird es so anzeigen:

<img src="/img/tutorial/query-params-str-validations/image01.png">