[v3 wrappers] Support arbitrary optional query parameters

オープン
  • 何か問題がありますか？
#3,897 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

@ramsessanchez がすでに取り組んでいます。

2026年11月6日 から。

  • #3900 @ramsessanchez による — オープン

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
35/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
csharp, powershell
領域
api, developer-experience

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.

主要言語
C#
スター
909
フォーク
234
平均マージ
3日 21時間
マージ済み PR（30日）
23

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

microsoftgraph/msgraph-sdk-powershell のほかの issue

microsoftgraph/msgraph-sdk-powershell の issue をすべて見る

似ている issue

C# の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。