-
Notifications
You must be signed in to change notification settings - Fork 50
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
Missing .suspend
/ .resume
definitions in durableClient.d.ts
#608
Comments
Is there a reason why to use |
cc/ @erizba in case you have cycles. @evanlouie I think we disabled tsc automatically emitting types to avoid the opposite problem: too many internally types being exposed, some by accident. In this case that's bitten us, but we've also been bit by the opposite behavior. |
This is biting me right now as well. I have the perfect use case for suspending and resuming my orchestrations but am unable to use the built-in functionality at present. 🤞 this is coming soon. |
Actually, is there any ETA on this? I was considering implementing this on my own using custom events, but I would much prefer to use the built-in functionality. Of course because it's code I don't have to write, but we also get a lot of value out of the orchestration status changing. If I implement this as a custom event, I lose the ability to inspect the state change, both on suspend and resume. If the original issue was correct, it seems like this is just a published types issue and not actually missing / new functionality required, and hopefully low-hanging fruit. Thanks! |
A couple of other hopefully useful notes, presumably missing for the same reasons:
|
Describe the bug
Looks like suspend/resume support was landed in 3.1.0 (#578) but durableClient.d.ts has not been updated to show the new methods.
Expected behavior
I should be able to see .suspend .resume on the
DurableClient
when coding in TypeScriptActual behavior
Compiler cannot see
.suspend
and.resume
because the d.ts file hasn't been updated.The text was updated successfully, but these errors were encountered: