Como eles são parte da URL, eles são "naturalmente" strings.

Mas quando você declara eles com os tipos do Python (no exemplo acima, como `int`), eles são convertidos para aquele tipo e validados em relação a ele.

Todo o processo que era aplicado para parâmetros de rota também é aplicado para parâmetros de consulta:

* Suporte do editor (obviamente)
* <abbr title="convertendo uma string que vem de um request HTTP em um dado Python">"Parsing"</abbr> de dados

    public boolean processHeartbeat(String registrationId, long sequenceNumber) {
        MockRegistration registration = registrations.get(registrationId);
        if (registration != null) {
            log.debug("Mock processed heartbeat for: {} seq: {}", registrationId, sequenceNumber);
            return true;
        }
        return false;
    }

        timestamp = (Date) ConfigUtils.getObject(session, new Date(), "maven.startTime");

        /*
         * NOTE: This should be considered a quirk to support interop with Maven's legacy ArtifactDeployer which
         * processes one artifact at a time and hence cannot associate the artifacts from the same project to use the
         * same version index. Allowing the caller to pass in metadata from a previous deployment allows to re-establish

import org.opensearch.index.query.QueryBuilders;

import jakarta.servlet.http.HttpServletRequest;

/**
 * Entity class that handles geographic information for search queries.
 * This class processes geographic query parameters from HTTP requests and converts them
 * into OpenSearch geo-distance queries for location-based search functionality.
 *
 */
public class GeoInfo {

    inflater.inflate(buffer)
    assertThat(buffer.readUtf8()).isEqualTo("Hello inflation!")
  }

  /**
   * It's possible a self-terminating deflated message will contain trailing data that won't be
   * processed during inflation. If this happens, we need to either reject the message or discard
   * the unreachable data. We choose to discard it!
   *

     * Represents an API response for bulk operations, containing a list of processed items.
     */
    public static class ApiBulkResponse extends ApiResponse {
        /**
         * Constructs an empty ApiBulkResponse.
         */
        public ApiBulkResponse() {
            // NOP
        }

        /**
         * The list of items processed in the bulk operation.
         */

        }

        snapshots = new LinkedHashMap<>();

        /*
         * NOTE: This should be considered a quirk to support interop with Maven's legacy ArtifactDeployer which
         * processes one artifact at a time and hence cannot associate the artifacts from the same project to use the
         * same timestamp+buildno for the snapshot versions. Allowing the caller to pass in metadata from a previous

     */
    public static class PropertiesReader extends LineNumberReader {
        /** Stores the comment lines for the currently processed property.*/
        private final List<String> commentLines;

        /** Stores the value lines for the currently processed property.*/
        private final List<String> valueLines;

        /** Stores the name of the last read property.*/
        private String propertyName;

     */
    public static class PropertiesReader extends LineNumberReader {
        /** Stores the comment lines for the currently processed property.*/
        private final List<String> commentLines;

        /** Stores the value lines for the currently processed property.*/
        private final List<String> valueLines;

        /** Stores the name of the last read property.*/
        private String propertyName;

## `bump-pydantic` { #bump-pydantic }

Em muitos casos, quando você usa modelos Pydantic regulares sem personalizações, será possível automatizar a maior parte do processo de migração do Pydantic v1 para o Pydantic v2.

Você pode usar o <a href="https://github.com/pydantic/bump-pydantic" class="external-link" target="_blank">`bump-pydantic`</a> da própria equipe do Pydantic.