searchPaging(data, form);
        });
    }

    /**
     * Search with paging.
     * @param data The render data.
     * @param form The search form.
     */
    protected void searchPaging(final RenderData data, final SearchForm form) {
        // page navi

/**
 * Search request body for data configuration administration.
 * Extends BaseSearchBody with data configuration-specific search parameters.
 */
public class SearchBody extends BaseSearchBody {

    /** The data configuration name to search for. */
    public String name;

    /** The handler name to search for in data configurations. */
    public String handlerName;

                                                <c:forEach var="data" varStatus="s"
                                                           items="${failureUrlItems}">
                                                    <tr data-href="${contextPath}/admin/failureurl/details/4/${f:u(data.id)}">
                                                        <td>${f:h(data.url)}</td>

    var button = $(event.relatedTarget);
    var docId = button.data("docid");
    var title = button.data("title");
    var url = button.data("url");

    $(this)
      .find(".modal-body #delete-doc-title")
      .text(title);
    $(this)
      .find(".modal-body #delete-doc-url")
      .text(url);
    $(this)
      .find(".modal-footer input#docId")
      .val(docId);
  });

Et seront aussi utilisés dans chaque *opération de chemin* de la documentation utilisant ces modèles :

<img src="/img/tutorial/body/image02.png">

## Support de l'éditeur

Dans votre éditeur, vous aurez des annotations de types et de l'auto-complétion partout dans votre fonction (ce qui n'aurait pas été le cas si vous aviez utilisé un classique `dict` plutôt qu'un modèle Pydantic) :

<img src="/img/tutorial/body/image03.png">

Static\n\n  static _jQueryInterface(config) {\n    let data = $(this).data(DATA_KEY)\n    const _options = $.extend({}, Default, $(this).data())\n\n    if (!data) {\n      data = new CardRefresh($(this), _options)\n      $(this).data(DATA_KEY, typeof config === 'string' ? data : config)\n    }\n\n    if (typeof config === 'string' && /load/.test(config)) {\n      data[config]()\n    } else {\n      data._init($(this))\n    }\n  }\n}\n\n/**\n * Data API\n * ====================================================\n...

It doesn't return a large `str` containing the data in JSON format (as a string). It returns a Python standard data structure (e.g. a `dict`) with values and sub-values that are all compatible with JSON.

/// note

`jsonable_encoder` is actually used by **FastAPI** internally to convert data. But it is useful in many other scenarios.

            searchPaging(data, form);
        });
    }

    /**
     * Search with paging.
     * @param data The render data.
     * @param form The search form.
     */
    protected void searchPaging(final RenderData data, final SearchForm form) {
        // page navi

                                    <tbody>
                                    <c:forEach var="data" varStatus="s" items="${dictFiles}">
                                        <tr data-href="${f:h(data.type)}/?dictId=${f:h(data.id)}">
                                            <td>${f:h(data.path)}</td>
                                            <td>${f:h(data.type)}</td>
                                        </tr>

        SMBUtil.writeInt2(17, buffer, bodyStart);
        // Data offset (byte - offset from header start)
        buffer[bodyStart + 2] = (byte) dataOffsetFromHeader;
        // Reserved
        buffer[bodyStart + 3] = 0;
        // Data length
        SMBUtil.writeInt4(dataLength, buffer, bodyStart + 4);
        // Data remaining
        SMBUtil.writeInt4(dataRemaining, buffer, bodyStart + 8);