Fix GenerateAssertion dropping parameter default values from generated extension methods - #4828
Conversation
thomhurst
commented
Feb 16, 2026
@claude There should be new snapshots for the new test |
Claude finished @thomhurst's task in 3m 26s —— View job Tasks
SummaryI've successfully created the missing snapshot files for the Created files:
All snapshots include the key line that the test validates: publicstaticStringArray_ContainsMessage_String_Bool_AssertionContainsMessage(thisIAssertionSource<string[]>source,stringneedle,boolexact=true, ...)Commit created: IssueI encountered a permission error when attempting to push the commit to the remote repository. The GitHub Actions bot doesn't have write permissions to this branch. To complete this task, you'll need to either:
The commit is ready and waiting in the local repository with proper co-authorship attribution. | Branch |
thomhurst
commented
Feb 16, 2026
@copilot There should be new snapshots for the new test |
Added 4 snapshot |
…ed extension methods Co-authored-by: thomhurst <30480171+thomhurst@users.noreply.github.com>
Co-authored-by: thomhurst <30480171+thomhurst@users.noreply.github.com>
22d9c2b to
97875c3CompareUh oh!
There was an error while loading. Please reload this page.
MethodAssertionGeneratordoesn't preserve default parameter values in generated extension methodsHasExplicitDefaultValueandDefaultValueExpressionfields toParameterDatarecord structParameterDatainstancesFormatDefaultValuehelper method toMethodAssertionGenerator(consistent with existing logic inAssertionExtensionGenerator)GenerateExtensionMethodOriginal prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.