Skip to content

Fix parameter ordering bug in TaskHubClient.cs#1219

Merged
cgillum merged 1 commit into
Azure:mainfrom
ajchalla:patch-1
May 21, 2025
Merged

Fix parameter ordering bug in TaskHubClient.cs#1219
cgillum merged 1 commit into
Azure:mainfrom
ajchalla:patch-1

Conversation

@ajchalla

Copy link
Copy Markdown
Contributor

Fixed a bug in CreateOrchestrationInstanceAsync where the startAt parameter was incorrectly passed as the 8th argument to InternalCreateOrchestrationInstanceWithRaisedEventAsync, which expects startAt as the 9th parameter.

Updated the method call to correctly pass startAt as the 9th argument, preserving the correct order of optional parameters

Fixed a bug in `CreateOrchestrationInstanceAsync` where the `startAt` parameter was incorrectly passed as the 8th argument to `InternalCreateOrchestrationInstanceWithRaisedEventAsync`, which expects `startAt` as the 9th parameter.

Updated the method call to correctly pass `startAt` as the 9th argument, preserving the correct order of optional parameters

@cgillum cgillum left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this fix! Indeed, it looks like this parameter was not correctly assigned (one of the reasons I wish we were using named parameters for these overloads).

@cgillum cgillum merged commit 1c09332 into Azure:main May 21, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants