Skip to content

Conversation

@cretz
Copy link
Member

@cretz cretz commented Jul 13, 2022

What was changed

Add the same high-level workflow execution description properties that TS has

Why?

Raw message is too cumbersome

@cretz cretz requested a review from a team July 13, 2022 14:07
close_time: Optional[datetime]
execution_time: Optional[datetime]
history_length: int
id: str
Copy link
Member

Choose a reason for hiding this comment

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

This should probably be workflow_id. It's that way in TS and you have to infer what it is by looking at run id and knowing there are two types of IDs, which seems less than ideal.

Copy link
Member Author

@cretz cretz Jul 13, 2022

Choose a reason for hiding this comment

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

In Python we have used id where it's obviously a workflow ID to avoid stuttering and unnecessary typing. So we have WorkflowHandle.id, start_workflow(id="myid") etc. This was how it was originally proposed/designed, but if we want to change all of these we can (I'd do it in a separate PR). I will bring it up.

Copy link
Member

@bergundy bergundy left a comment

Choose a reason for hiding this comment

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

Nothing blocking

@cretz cretz merged commit 232446a into temporalio:main Jul 14, 2022
@cretz cretz deleted the describe-details branch July 14, 2022 17:55
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.

3 participants