title="Floating point number" required="required"
                                                 data-validation="custom"
                                                 data-validation-regexp="(\+|\-)?\d+(\.\d+)?((e|E)(\+|\-)?\d+)?"
                                                 data-validation-help="number (Float)"/>

 * the symmetry of {@code equals}. Custom definitions of equality are usually based on an interface,
 * such as {@code Set} or {@code List}, so that the implementation of {@code equals} can cast the
 * object being tested for equality to the custom interface. {@code ForwardingObject} implements no
 * such custom interfaces directly; they are implemented only in subclasses. Therefore, forwarding

        "type": "prometheus",
        "uid": "${DS_PROMETHEUS}"
      },
      "fieldConfig": {
        "defaults": {
          "color": {
            "mode": "palette-classic"
          },
          "custom": {
            "axisBorderShow": false,
            "axisCenteredZero": false,
            "axisColorMode": "text",
            "axisLabel": "",
            "axisPlacement": "auto",
            "barAlignment": 0,

        // Verify that exception was handled
        assertTrue(exceptionHandled.get());
    }

    // Test with a custom ClassLoader to simulate class availability
    public void test_hook_withCustomClassLoader() throws Exception {
        // Create a custom ClassLoader that can control class loading behavior
        ClassLoader customClassLoader = new URLClassLoader(new URL[0], null) {
            @Override

    }

    @Test
    @DisplayName("Test custom implementation with signing not enforced")
    void testCustomImplementationSigningNotEnforced() {
        // Given
        SmbNegotiationRequest request = new TestSmbNegotiationRequest(false);

        // When
        boolean result = request.isSigningEnforced();

        // Then
        assertFalse(result, "Custom implementation should return false when initialized with false");

Nevertheless, we can declare the expected schema for the request body.

### Custom OpenAPI content type { #custom-openapi-content-type }

Using this same trick, you could use a Pydantic model to define the JSON Schema that is then included in the custom OpenAPI schema section for the *path operation*.

And you could do this even if the data type in the request is not JSON.

        "type": "prometheus",
        "uid": "${DS_PROMETHEUS}"
      },
      "fieldConfig": {
        "defaults": {
          "color": {
            "mode": "palette-classic"
          },
          "custom": {
            "axisBorderShow": false,
            "axisCenteredZero": false,
            "axisColorMode": "text",
            "axisLabel": "",
            "axisPlacement": "auto",
            "barAlignment": 0,

            }
        };

        assertEquals("Custom protocolType should be WEB", ProtocolType.WEB, customAnnotation.protocolType());
        assertEquals("Custom message should match", "Test message", customAnnotation.message());
        assertEquals("Custom groups should have one element", 1, customAnnotation.groups().length);
        assertEquals("Custom payload should have one element", 1, customAnnotation.payload().length);

{* ../../docs_src/middleware/tutorial001.py hl[8:9,11,14] *}

/// tip | Consejo

Ten en cuenta que los custom proprietary headers se pueden añadir <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers" class="external-link" target="_blank">usando el prefijo 'X-'</a>.

        assertFalse(user.isEditable());
    }

    public void test_isEditable_custom() {
        // Test custom implementation that returns true
        FessUser user = new TestEditableFessUser("testuser", true);
        assertTrue(user.isEditable());

        // Test custom implementation that returns false
        user = new TestEditableFessUser("testuser", false);
        assertFalse(user.isEditable());