fix: prevent crash when package-name option is missing in http-client-csharp#1
Closed
JonathanCrd wants to merge 1 commit intomainfrom
Closed
fix: prevent crash when package-name option is missing in http-client-csharp#1JonathanCrd wants to merge 1 commit intomainfrom
JonathanCrd wants to merge 1 commit intomainfrom
Conversation
…-csharp - Make package-name optional in C# Configuration with default fallback - Resolve default from PrimaryNamespace in Configure() with info message - Report diagnostics instead of throwing when C# generator fails - Remove ReadRequiredStringOption since no options are required anymore - Add tests for default package name behavior and diagnostic reporting Fixes microsoft#9554 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
JonathanCrd
pushed a commit
that referenced
this pull request
Apr 9, 2026
…icrosoft#9713) Upgrades http-client-python dependencies to match root package.json versions for consistency across the monorepo. ## Dependencies Updated - **@types/node**: ~24.1.0 → ~25.0.2 - **rimraf**: ~6.0.1 → ~6.1.2 - **tsx**: ~4.19.1 → ^4.21.0 - **typescript**: ~5.8.2 → ~5.9.2 - **typescript-eslint**: ^8.21.0 → ^8.49.0 - **vitest**: ^3.1.2 → ^4.0.15 ## Changes - Updated `packages/http-client-python/package.json` with aligned versions - Regenerated `package-lock.json` via `npm install` - Added changelog entry with `changeKind: dependencies` <!-- START COPILOT ORIGINAL PROMPT --> <details> <summary>Original prompt</summary> update dependencies of packages/http-client-python/package.json. If they are found it package.json, upgrade to same version. NOTE: PR title shall starts with "[python]" <analysis> [Chronological Review: - The user provided a timestamp and requested: **“clean all changes”**. - Assistant initiated a parallel tool call with: 1) `functions.report_intent` (intent logging), and 2) `functions.powershell` to run a git cleanup command chain. - PowerShell command executed: `git --no-pager status --short && git reset --hard HEAD && git clean -fd && git --no-pager status --short` - Tool output showed there was a modified file before reset (`M packages/http-client-python/package.json`), then successful hard reset to commit `efbf17ff8`, and successful completion (exit code 0). - Assistant then ran a second verification command: `git --no-pager status --short` which returned no output and exit code 0 (clean working tree). - Assistant called `functions.task_complete` with a summary indicating all tracked/untracked changes were removed and cleanliness verified. - Assistant replied to user: repo is clean. - User then asked for a structured conversation summary emphasizing recent commands/tool results.] [Intent Mapping: - Explicit user request #1: **“clean all changes”** (clear local tracked and untracked changes). - Explicit user request microsoft#2: Summarize conversation history with emphasis on recent commands/results and no additional tool calls. - Implicit expectation: confirm repo cleanliness after cleanup and provide a handoff-quality summary.] [Technical Inventory: - Version control: **Git**. - Commands used: `git status --short`, `git reset --hard HEAD`, `git clean -fd`. - Agent tooling: `multi_tool_use.parallel`, `functions.report_intent`, `functions.powershell`, `functions.task_complete`. - Environment note from user reminder: no SQL tables currently exist; SQL tool was not used.] [Code Archaeology: - Mentioned file: `packages/http-client-python/package.json` (was modified before cleanup). - No new code edits were made; all local edits were discarded. - Repository state restored to `HEAD` commit `efbf17ff8` with no remaining local diffs/untracked files.] [Progress Assessment: - Completed: workspace cleanup and verification. - Pending: none from original cleanup task. - New active task: produce detailed structured summary (current response).] [Context Validation: - Captured user goals, all tool calls, exact command strings, key outputs, and final repo state. - Captured immediate pre-summary state (cleanup completed, user requested summary). - Noted that summarization was user-triggered; no evidence of an actual runtime token-overflow event in the visible transcript.] [Recent Commands Analysis: - Last agent commands executed: - `functions.report_intent` with `intent: "Cleaning workspace"` → result: “Intent logged”. - `functions.powershell` command chain for cleanup and status checks. - Follow-up `functions.powershell` with `git --no-pager status --short` for explicit verification. - `functions.task_complete` with cleanup summary. - Key tool results: - Pre-clean status included `M packages/http-client-python/package.json`. - `git reset --hard HEAD` succeeded: `HEAD is now at efbf17f ...`. - Final status checks returned clean output (empty `git status --short`), exit code 0. - Immediate pre-summarization state: task already completed and user-confirmed response sent; then user requested this summary.] </analysis> <summary> 1. Conversation Overview: - Primary Objectives: - User requested: **“clean all changes”**. - Later requested: **“Summarize the conversation history so far, paying special attention to the most recent agent commands and tool results...”** - Session Context: - Single operational task session: detect local changes, discard everything, verify clean state, report completion. - User Intent Evolution: - Started with repo cleanup. - Shifted to documentation/handoff summary of what was executed and what results were returned. 2. Technical Foundation: - Git CLI: - Used to inspect and forcibly restore working tree state. - Agent Tooling: - `multi_tool_use.parallel` for concurrent intent logging + shell action. - `functions.powershell` for command execution. - `functions.task_complete` for formal completion marker. - Workflow Pattern: - Execute destructive cleanup (`reset --hard` + `clean -fd`) then verify with explicit status check. - Environment Detail: - User reminder included SQL tool note (“No tables currently exist...”), but no SQL operations were performed. 3. Codebase Status: - `packages/http-client-python/package.json`: - Purpose: package metadata/config for python HTTP client package. - Current State: previously modified; modification discarded by hard reset. - Key Code Segments: none discussed. - Dependencies: only r... </details> <!-- START COPILOT CODING AGENT SUFFIX --> Created from Copilot CLI via the copilot delegate command. <!-- START COPILOT CODING AGENT TIPS --> --- 💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more [Copilot coding agent tips](https://gh.io/copilot-coding-agent-tips) in the docs. --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: msyyc <70930885+msyyc@users.noreply.github.com> Co-authored-by: Yuchao Yan <yuchaoyan@microsoft.com>
|
No changes needing a change description found. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
When running the C# emitter with no options (specifically no
package-name), the C# generator crashes with anInvalidOperationExceptioninstead of reporting a diagnostic or using a default.Changes
C# Generator
Configuration.cs: Madepackage-nameoptional with aDefaultPackageNamefallback ("GeneratedClient"). RemovedReadRequiredStringOptionsince no options are required anymore.CodeModelGenerator.cs: InConfigure(), resolves the default fromPrimaryNamespace(code model namespace) and emits an info message — per Josh's suggestion.TypeScript Emitter
emitter.ts: Generator failures now report diagnostics viasdkContext.logger.error()instead of throwing unhandled exceptions.Tests
ConfigurationTests.cs: verify default package name behavior and PrimaryNamespace resolution.Fixes microsoft#9554
🤖 Created with JonathanCrd copilot