Skip to content

Accept DateTimeOffset for workflow start time #1583

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: release-1.16
Choose a base branch
from

Conversation

frankbuckley
Copy link
Contributor

Adds overload to DaprWorkflowClient.ScheduleNewWorkflowAsync accepting a DateTimeOffset? value for startTime.

Note: I have included the documentation change from #1581 and also included it on the new overload.

Issue reference

#1576

Checklist

Please make sure you've completed the relevant tasks for this PR, out of the following list:

  • Code compiles correctly
  • Created/updated tests
  • Extended the documentation

- Adds overload to DaprWorkflowClient.ScheduleNewWorkflowAsync accepting a DateTimeOffset? value for startTime
- Resolves dapr#1576

Signed-off-by: Frank Buckley <[email protected]>
@frankbuckley frankbuckley requested review from a team as code owners July 10, 2025 16:02
@frankbuckley
Copy link
Contributor Author

Will revisit

Signed-off-by: Frank Buckley <[email protected]>
@frankbuckley
Copy link
Contributor Author

Requiring the parameters on the new overload raises the question again of whether to replace the DateTime? on the existing overload. It is a binary breaking change, but on recompilation there will be a default conversion to DateTimeOffset (as happens now under the covers).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants