[v3 wrappers] Support arbitrary optional query parameters

未关闭
  • 哪里不对？
#3,897 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@ramsessanchez 已经在做这个了。

开始于 2026年11月6日。

  • #3900 来自 @ramsessanchez —— 未关闭

评估

难度
5/5
预计耗时
一周以上
新手友好度
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 小时
30 天内合并 PR
23

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

microsoftgraph/msgraph-sdk-powershell 的其他 Issue

查看 microsoftgraph/msgraph-sdk-powershell 的全部 Issue

相似的 Issue

更多 C# Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。