def test_swagger_ui():
    response = client.get("/docs")
    assert response.status_code == 200, response.text
    assert '"syntaxHighlight": false' in response.text, (
        "syntaxHighlight should be included and converted to JSON"
    )
    assert '"dom_id": "#swagger-ui"' in response.text, (
        "default configs should be preserved"
    )
    assert "presets: [" in response.text, "default configs should be preserved"

 * similar to the way Maven configures plugins from the POM, i.e. some configuration like {@code <param>value</param>}
 * is mapped to an equally named property of the bean and converted. The properties of the bean are supposed to either
 * have a public setter or be backed by an equally named field (of any visibility).
 *
 * @since 3.0
 */
public interface BeanConfigurator {

    /**

public interface ReportingConverter {

    /**
     * Converts values from model's reporting section into the configuration for Maven Site Plugin 3.x.
     *
     * @param model The model whose reporting section should be converted, must not be <code>null</code>.
     * @param request The model building request that holds further settings, must not be {@code null}.

  private static final char CASE_MASK = 0x20;

  /**
   * Returns a copy of the input string in which all {@linkplain #isUpperCase(char) uppercase ASCII
   * characters} have been converted to lowercase. All other characters are copied without
   * modification.
   */
  public static String toLowerCase(String string) {
    int length = string.length();
    for (int i = 0; i < length; i++) {

     * @throws InstantiationRuntimeException if the class declaring the constructor is abstract
     * @throws IllegalAccessRuntimeException if the number of actual and formal parameters differ, if primitive arguments cannot be converted, or if the class is related to enums
     * @see Constructor#newInstance(Object[])
     */
    public static <T> T newInstance(final Constructor<T> constructor, final Object... args)

* `skip`: with a value of `0`
* `limit`: with a value of `10`

As they are part of the URL, they are "naturally" strings.

But when you declare them with Python types (in the example above, as `int`), they are converted to that type and validated against it.

All the same process that applied for path parameters also applies for query parameters:

* Editor support (obviously)

        return null;
    }

    /**
     * Returns a {@link ConstructorDesc} that matches the given arguments.
     * <p>
     * If the parameter type is a number, it is considered a match if the argument can be converted to the number type.
     * </p>
     *
     * @param args
     *            the constructor arguments
     * @return a {@link ConstructorDesc} that matches the arguments, or {@literal null} if none exists
     */

    /**
     * A map for URL conversion.
     */
    protected Map<String, String> convertMap = new LinkedHashMap<>();

    /**
     * Converts a URL.
     *
     * @param url The URL.
     * @return A converted URL.
     */
    public String convert(final String url) {
        if (url == null) {
            return null;
        }
        String convertedUrl = url;

    }

    /**
     * Test the getEntries() method with a populated DfsEnumArray200.
     * Verifies that the DFS entries are correctly converted to FileEntry objects.
     */
    @Test
    void testGetEntries() {
        // Given
        MsrpcDfsRootEnum dfsRootEnum = new MsrpcDfsRootEnum("test-server");

* `frozenset`:
    * In requests and responses, treated the same as a `set`:
        * In requests, a list will be read, eliminating duplicates and converting it to a `set`.
        * In responses, the `set` will be converted to a `list`.
        * The generated schema will specify that the `set` values are unique (using JSON Schema's `uniqueItems`).
* `bytes`:
    * Standard Python `bytes`.
    * In requests and responses will be treated as `str`.