Provide last result and last failure to workflows #635
Description
Describe the solution you'd like
Go, Java, and TypeScript all provide a way to get the "last result" and "last failure" if this was via cron or schedule (come over in workflow start history as last_completion_result and continued_failure). Newer SDKs should too.
Even though this is immutable data and was put on TypeScript as info, Go and Java have this directly on the workflow context and it'll make sense for newer SDKs to do the same. Also make sure there is an obvious way to differentiate the absence of a "last result" and a null one.
Also, although it's technically an array in history/Core, langs should treat this as a single value.
Per-SDK Tickets
- Go - Done
- Java - Done
- Core - Done
- TypeScript - Done
- Python - [Feature Request] Provide last result and last failure to workflows sdk-python#383
- .NET - [Feature Request] Provide last result and last failure to workflows sdk-dotnet#489
- Ruby - [Feature Request] Provide last result and last failure to workflows sdk-ruby#281
- PHP - Done (maybe missing last error?)
- Temporal CLI - N/A