Use `StepError`s for unhandled error catching

inngest / inngest-js

The developer platform for easily building reliable workflows with zero infrastructure for TypeScript & JavaScript

https://www.inngest.com/

GNU General Public License v3.0

440 stars 43 forks source link

Use `StepError`s for unhandled error catching #474

Closed jpwilliams closed 9 months ago

jpwilliams commented 9 months ago

Summary

Aligns with the spec for throwing errors when memoizing data. This previous solution was for the initial release of step.invoke() pre-per-step errors.

Functionally there is no change, though the UI will no longer show NonRetriableError prefixes and will prefer user error data.

Checklist

[ ] ~~Added a docs PR that references this PR~~ N/A
[x] Added unit/integration tests
[x] Added changesets if applicable

changeset-bot[bot] commented 9 months ago

🦋 Changeset detected

Latest commit: 461adb4558a2a52f16b285a416ec040712a6a651

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

| Name | Type | | ------- | ----- | | inngest | Patch |

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

inngest-release-bot commented 9 months ago

A user has added the prerelease/inngest label, so this PR will be published to npm with the tag pr-474. It will be updated with the latest changes as you push commits to this PR.

You can install this prerelease version with:

npm install inngest@pr-474

The last release was built and published from 461adb4558a2a52f16b285a416ec040712a6a651.