[v3 wrappers] Support arbitrary optional query parameters

Abierto
  • ¿Algo no está bien?
#3,897 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@ramsessanchez ya está trabajando en esto.

Desde el 6/11/2026.

  • #3900 de @ramsessanchez — abierto

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
csharp, powershell
Área
api, developer-experience

Línea de trabajo

This is tracking only and names no implementation files or tests. Start by reading #3882 and the v3 generator's OpenAPI operation handling to map how query parameters reach generated cmdlets. Done means a follow-up covers optional parameters across supported operation families and methods, preserves existing behavior, and adds the listed generation and transport regressions.

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

Descripción

status:waiting-for-triage type:feature
Is your feature request related to a problem? Please describe the problem.

The v3 wrapper generator currently exposes a predefined set of optional OData query options where the operation and emitter support them, such as $filter, $select, $expand, $orderby, $search, $top, $skip, and $count.

Other optional query parameters declared in an operation's OpenAPI contract are not automatically exposed as cmdlet parameters, even when the generated Kiota client supports them. For example, an operation declaring an optional mode, locale, or includeArchived query cannot necessarily receive that input through its generated cmdlet. These names are illustrative, not claims about particular Graph endpoints.

The required-query work in #3882 is separate: it adds mandatory -Query<Name> inputs for required queries and deliberately does not broaden arbitrary optional-query support.

Describe the solution you'd like.

Track a future enhancement to generate and bind supported arbitrary optional query parameters from the effective OpenAPI operation contract across supported operation families and HTTP methods.

Acceptance criteria for that follow-up:

  • Expose optional inputs as nonmandatory cmdlet parameters and bind them through Kiota's typed query properties, preserving the API wire name and encoding.
  • Send an optional query only when the caller supplies it; preserve explicitly supplied false and 0 rather than treating them as omission. Define null/empty and array behavior consistently with the supported schema contract.
  • Honor inherited path-item parameters, operation-level overrides, supported types, and naming/collision rules. Consider the Query<Name> convention from #3882 for newly exposed inputs without breaking existing standard OData names and aliases or generating duplicates.
  • Preserve request bodies, headers, confirmation behavior, API-profile/cloud routing, and each operation's independent query contract, including PATCH refetch and pagination/delta continuation handling.
  • Add generated-code and compiled transport/binder regressions covering representative GET and mutation operations, omitted versus bound values, encoding, and collisions. Document any unsupported contracts explicitly.

This issue is tracking only. Do not implement as part of filing it or expand #3882 to include this work.

Additional context?

Parent release tracker: #3874 — Tracking for V3 Upgrade.

Related required-query work: #3882.

This is a v3 generator/API-coverage follow-up, not a claim that every optional query is currently unsupported. Existing supported optional OData behavior must remain intact. Track release disposition in the v3 upgrade issue; this filing alone does not classify the enhancement as a release blocker.

Lenguaje dominante
C#
Estrellas
909
Forks
234
Merge medio
3 d 21 h
PR fusionados (30 d)
23

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 microsoftgraph/msgraph-sdk-powershell

Todos los issues de microsoftgraph/msgraph-sdk-powershell

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.