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

Et vous obtenez aussi de la vérification d'erreur pour les opérations incorrectes de types :

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

Ce n'est pas un hasard, ce framework entier a été bâti avec ce design comme objectif.

Et cela a été rigoureusement testé durant la phase de design, avant toute implémentation, pour s'assurer que cela fonctionnerait avec tous les éditeurs.

Você também obterá preenchimento automático para o corpo a ser enviado:

<img src="/img/tutorial/generate-clients/image03.png">

/// tip | Dica

Observe o preenchimento automático para `name` e `price`, que foi definido na aplicação FastAPI, no modelo `Item`.

///

Você terá erros em linha para os dados que você envia:

<img src="/img/tutorial/generate-clients/image04.png">

    checkArgument(
        result == (int) result,
        "the total number of elements (%s) in the arrays must fit in an int",
        result);
    return (int) result;
  }

  /**
   * Returns a big-endian representation of {@code value} in an 8-element byte array; equivalent to
   * {@code ByteBuffer.allocate(8).putLong(value).array()}. For example, the input value {@code

```Python
async with lifespan(app):
    await do_stuff()
```

Cuando creas un context manager o un async context manager como arriba, lo que hace es que, antes de entrar al bloque `with`, ejecutará el código antes del `yield`, y al salir del bloque `with`, ejecutará el código después del `yield`.

        assertEquals((byte) 'S', SMBUtil.SMB2_HEADER[1]);
        assertEquals((byte) 'M', SMBUtil.SMB2_HEADER[2]);
        assertEquals((byte) 'B', SMBUtil.SMB2_HEADER[3]);

        // Verify structure size (64 in little-endian)
        assertEquals((byte) 64, SMBUtil.SMB2_HEADER[4]);
        assertEquals((byte) 0x00, SMBUtil.SMB2_HEADER[5]);
    }

    @ParameterizedTest

        assertEquals(4, bytesWritten);
        assertEquals(SmbComTransaction.TRANS_PEEK_NAMED_PIPE, buffer[offset]);
        assertEquals((byte) 0x00, buffer[offset + 1]);

        // Verify FID is written correctly (little-endian)
        int writtenFid = SMBUtil.readInt2(buffer, offset + 2);
        assertEquals(TEST_FID, writtenFid);
    }

    @Test
    @DisplayName("writeSetupWireFormat should handle buffer boundary")

    private static byte[] buildHeader(int status) {
        byte[] hdr = new byte[64]; // SMB2 header is 64 bytes
        System.arraycopy(SMBUtil.SMB2_HEADER, 0, hdr, 0, 64);
        // Write Status (little-endian) at offset 8 in the SMB2 header
        SMBUtil.writeInt4(status, hdr, 8);
        // Write Command = SMB2_IOCTL (0x000B) at offset 12
        SMBUtil.writeInt2(0x000B, hdr, 12);

        writeLittleEndianInt(dos, 0); // unusedChars
        writeLittleEndianInt(dos, totalChars); // usedChars

        // Write the actual characters (as shorts in little-endian)
        for (char c : testString.toCharArray()) {
            writeLittleEndianShort(dos, (short) c);
        }

        ByteArrayInputStream bais = new ByteArrayInputStream(baos.toByteArray());

        DummyResponse d = new DummyResponse();
        // Construct a minimal wire format buffer
        byte[] buf = new byte[32];
        int idx = 0;
        // Write values little-endian
        buf[idx++] = 5; // totalParameterCount low byte
        buf[idx++] = 0; // totalParameterCount high byte -> value 5
        buf[idx++] = 3; // totalDataCount low
        buf[idx++] = 0; // totalDataCount high

        @DisplayName("Should handle signed byte value correctly")
        void testReadBytesWireFormatSignedByteValue() {
            // Given
            byte[] buffer = new byte[10];
            // Write 4 in little-endian format
            buffer[0] = 0x04;
            buffer[1] = 0x00;

            // When & Then
            assertDoesNotThrow(() -> {
                int bytesRead = response.readBytesWireFormat(buffer, 0);