[v3 wrappers] Support arbitrary optional query parameters

Aberta
  • Algo errado?
#3,897 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

@ramsessanchez já está trabalhando nisso.

Desde 6/11/2026.

  • #3900 de @ramsessanchez — aberto

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
35/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
csharp, powershell
Domínio
api, developer-experience

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
C#
Estrelas
909
Forks
234
Merge médio
3d 21h
PRs com merge (30d)
23

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de microsoftgraph/msgraph-sdk-powershell

Todas as issues de microsoftgraph/msgraph-sdk-powershell

Issues semelhantes

Mais issues de C#

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.