Converter<String, Integer> converter = Ints.stringConverter();
    assertThat(converter.convert("1")).isEqualTo(1);
    assertThat(converter.convert("0")).isEqualTo(0);
    assertThat(converter.convert("-1")).isEqualTo(-1);
    assertThat(converter.convert("0xff")).isEqualTo(255);
    assertThat(converter.convert("0xFF")).isEqualTo(255);
    assertThat(converter.convert("-0xFF")).isEqualTo(-255);

  }

  public void testStringConverter_convert() {
    Converter<String, Double> converter = Doubles.stringConverter();
    assertThat(converter.convert("1.0")).isEqualTo(1.0);
    assertThat(converter.convert("0.0")).isEqualTo(0.0);
    assertThat(converter.convert("-1.0")).isEqualTo(-1.0);
    assertThat(converter.convert("1")).isEqualTo(1.0);
    assertThat(converter.convert("0")).isEqualTo(0.0);

    // ----------------------------------------------------------------------

    /**
     * Parses a sequence of XML elements and converts them to the given target type.
     *
     * @param parser The XML parser
     * @param toType The target type
     * @return Converted instance of the target type
     */
    private Object parse(final MXParser parser, final TypeLiteral<?> toType) throws Exception {

Comme ils font partie de l'URL, ce sont « naturellement » des chaînes de caractères.

Mais lorsque vous les déclarez avec des types Python (dans l'exemple ci-dessus, en tant que `int`), ils sont convertis vers ce type et validés par rapport à celui-ci.

Tous les mêmes processus qui s'appliquaient aux paramètres de chemin s'appliquent aussi aux paramètres de requête :

* Prise en charge de l'éditeur (évidemment)

     */
    protected LongConversionUtil() {
    }

    /**
     * Converts the given object to a {@link Long}.
     *
     * @param o
     *            the object to convert
     * @return the converted {@link Long}
     */
    public static Long toLong(final Object o) {
        return toLong(o, null);
    }

    /**
     * Converts the given object to a {@link Long}.
     *
     * @param o

For example, you cannot put a Pydantic model in a `JSONResponse` without first converting it to a `dict` with all the data types (like `datetime`, `UUID`, etc) converted to JSON-compatible types.

For those cases, you can use the `jsonable_encoder` to convert your data before passing it to a response:

    assertEquals((Integer) 2, converter.convert("two"));
    assertThrows(IllegalArgumentException.class, () -> converter.convert("three"));

    biMap.put("three", 3);

    assertEquals((Integer) 1, converter.convert("one"));
    assertEquals((Integer) 2, converter.convert("two"));
    assertEquals((Integer) 3, converter.convert("three"));
  }

     */
    void setValue(Object target, Object value);

    /**
     * Converts the value to the appropriate type if necessary based on the property type.
     *
     * @param <T>
     *            the converted type
     * @param value
     *            the value to be converted
     * @return the converted value
     */
    <T> T convertIfNeed(Object value);

    /**

        constants = populateCache(enumClass);
      }
      return constants;
    }
  }

  /**
   * Returns a serializable converter that converts between strings and {@code enum} values of type
   * {@code enumClass} using {@link Enum#valueOf(Class, String)} and {@link Enum#name()}. The
   * converter will throw an {@code IllegalArgumentException} if the argument is not the name of any
   * enum constant in the specified enum.
   *

Por exemplo, ele não recebe objetos `datetime`, pois estes objetos não são compatíveis com JSON.

Então, um objeto `datetime` teria que ser convertido em um `str` contendo os dados no [formato ISO](https://en.wikipedia.org/wiki/ISO_8601).

Da mesma forma, este banco de dados não receberia um modelo Pydantic (um objeto com atributos), apenas um `dict`.