Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Return generated model instances from connector operations

Cerrado
  • ¿Algo no está bien?
#92 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
backend-api-design, tooling

Línea de trabajo

Start with the CodefulSdkGenerator and the pinned managed connector contracts to trace how operation return annotations and JSON responses are currently emitted. Review the required serialization/deserialization coverage for nested models, collections, optional fields, and wire-name mappings. Done means affected clients return generated model instances where schemas exist, preserve other response behaviors, pass the stated tests, and match the paired generator revision.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Problem

Generated connector clients expose response model classes, but operation methods currently deserialize JSON responses to weak dictionary types. For example, Office365Client.get_emails_async returns dict[str, Any] | None rather than an instance of its generated response model. This prevents callers and documentation from relying on typed response properties.

Identified in PR #89 review.

Proposed work

  • Update the CodefulSdkGenerator to emit precise operation return annotations when the managed connector contract defines a response schema.
  • Deserialize JSON responses into the corresponding generated model classes, including nested models, collections, optional fields, and wire-name mappings.
  • Preserve dictionary, binary, text, and empty-response behavior when no generated response model applies.
  • Regenerate affected connector clients from pinned contracts and link the paired AzureUX-BPM generator PR.
  • Update API documentation after typed responses are available.

Acceptance criteria

  • Connector operations with modeled response schemas return generated model instances rather than dict[str, Any].
  • Return annotations distinguish modeled, unmodeled, binary, text, and no-content responses.
  • Serialization/deserialization tests cover nested objects, collections, optional fields, and wire-name mappings.
  • Existing connector behavior remains compatible for responses without modeled schemas.
  • Generated artifacts match the paired generator revision.
Lenguaje dominante
Python
Estrellas
0
Forks
3
Merge medio
3 d 11 h
PR fusionados (30 d)
10

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Azure/connectors-python-sdk

Todos los issues de Azure/connectors-python-sdk

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.