}

    // PUT /api/admin/fileconfig/setting
    /**
     * Updates an existing file configuration setting.
     *
     * @param body file configuration setting data to update
     * @return JSON response with updated setting ID and status
     */
    @Execute
    public JsonResponse<ApiResult> put$setting(final EditBody body) {
        validateApi(body, messages -> {});

But when you import `Query`, `Path`, `Depends`, `Security` and others from `fastapi`, those are actually functions that return special classes.

///

## Use `SecurityScopes` { #use-securityscopes }

Now update the dependency `get_current_user`.

This is the one used by the dependencies above.

Here's where we are using the same OAuth2 scheme we created before, declaring it as a dependency: `oauth2_scheme`.

            request.setMinimumCount(100);

            // Update parameters
            request.setReadLength(2000);
            request.setOffset(1000L);
            request.setMinimumCount(200);
            request.setRemainingBytes(3000);
            request.setPadding((byte) 4);
            request.setReadFlags((byte) 0x02);

            // Update file ID
            byte[] newFileId = new byte[16];

import org.opensearch.transport.client.Client;

/**
 * The AnalyzerSettings class is responsible for managing and configuring analyzers for different fields and languages.
 * It interacts with the OpenSearch client to create, update, and delete analyzer settings, as well as to retrieve
 * analyzer names and mappings.
 *
 * <p>Key functionalities include:</p>
 * <ul>
 *   <li>Initializing analyzer settings and mappings.</li>

 * <li>High-level helpers (addGAVElements, createDependency, createPlugin)</li>
 * <li>Null-safe operations (updateElementContent, removeElement)</li>
 * <li>Update-or-create patterns (updateOrCreateChildElement)</li>
 * </ul>
 *
 * @see eu.maveniverse.domtrip.Element
 * @see eu.maveniverse.domtrip.Editor
 * @see eu.maveniverse.domtrip.maven.PomEditor
 */
public class DomUtils {

	// Endpoint is the replication target endpoint
	Endpoint string `json:"-"`
	// Secure is true if the replication target endpoint is secure
	Secure bool `json:"-"`
}

func (sr *SRStats) update(st replStat, dID string) {
	sr.lock.Lock()
	defer sr.lock.Unlock()
	srs, ok := sr.M[dID]
	if !ok {
		srs = &SRStatus{
			XferRateLrg: newXferStats(),
			XferRateSml: newXferStats(),
		}
	}

     *
     * @param form the edit form containing updated settings
     * @return HTML response after updating settings
     */
    @Execute
    @Secured({ ROLE })
    public HtmlResponse update(final EditForm form) {
        validate(form, messages -> {}, () -> asHtml(path_AdminGeneral_AdminGeneralJsp));
        verifyToken(() -> asHtml(path_AdminGeneral_AdminGeneralJsp));

        updateConfig(fessConfig, form);

</div>

その後 `/docs` の UI にアクセスすると、FastAPI がこれらのモデルを使って API をドキュメント化し、同時にデータのシリアライズとバリデーションにも使っていることがわかります。

<div class="screenshot">
<img src="/img/tutorial/sql-databases/image01.png">
</div>

## 複数モデルでアプリを更新 { #update-the-app-with-multiple-models }

ここで、少しリファクタリングしてセキュリティと汎用性を高めましょう。

前のアプリでは、UI 上でクライアントが作成する `Hero` の `id` を自分で決められてしまいます。😱

    }

    /**
     * Updates an existing label type setting.
     *
     * @param body the label type data to update
     * @return JSON response containing the updated label type setting ID
     */
    // PUT /api/admin/labeltype/setting
    @Execute
    public JsonResponse<ApiResult> put$setting(final EditBody body) {

        }

        // Call the method
        int bytesRead = response.readBytesWireFormat(guid, 0);

        // Assertions
        // When CAP_EXTENDED_SECURITY is set, it only copies GUID but doesn't update bufferIndex
        assertEquals(0, bytesRead);
        assertArrayEquals(guid, serverData.guid);
        assertEquals("", serverData.oemDomainName);
    }

    @Test