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
[queues] correct DurableObject
to DurableObjectNamespace
& remove constructor block
#14529
[queues] correct DurableObject
to DurableObjectNamespace
& remove constructor block
#14529
Conversation
Thanks for the PR. There's a small snag with the |
@garysassano should be fixed, now returns a 400 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Better to change the properties to be private.
Co-authored-by: Maddy <130055405+Maddy-Cloudflare@users.noreply.github.com>
… constructor block (cloudflare#14529) * correct `DurableObject` to `DurableObjectNamespace` * remove constructor block and made `env` public * add failure response * Update content/queues/examples/use-queues-with-durable-objects.md Co-authored-by: Maddy <130055405+Maddy-Cloudflare@users.noreply.github.com> --------- Co-authored-by: Maddy <130055405+Maddy-Cloudflare@users.noreply.github.com>
In the
Env
declaration for the Use Queues with Durable Objects example, theYOUR_DO_CLASS
binding should be an instance ofDurableObjectNamespace
instead ofDurableObject
.Constructor block for the
YourDurableObject
class contained an extra}
, causing thefetch()
to not be recognized. This block has been removed entirely, and theenv
been madepublic
to matchstate