feat: clarify error messages around durable objects beta #1921
Conversation
| let status = res.status(); | ||
| if !status.is_success() { | ||
| let text = res.text()?; | ||
| if text.contains("workers.api.error.not_entitled") { |
There was a problem hiding this comment.
Is durable objects the only possible reason for not_entitled?
There was a problem hiding this comment.
Probably not, but it's a temp quick fix until you get DO's to GA.
There was a problem hiding this comment.
Then is there a reason not to show the original error plus a "If you are trying to use Modules, you need to opt in..."?
As it stands someone's probably going to be more confused, not less, if it has nothing to do with modules or DO
There was a problem hiding this comment.
I'd think there would be a better API error, actually indicating the accurate entitlement missing. But I'm assuming you're not ready to commit to that until GA..
The original error was "Something went wrong!" + the ambiguous workers.api.error.not_entitled.
Co-authored-by: Ashcon Partovi <[email protected]>
Disambiguates error message described in #1859, adds more clarity around other places where Durable Object usage in beta may conflict with
wranglerfunctionality.