Skip to content

Standardized get wrapper error handling; NotFoundError no longer passes through

Choose a tag to compare

View all tags
released this 25 Oct 16:07
· 34 commits to working since this release
v4.4.54
1eaf6b1

This release focuses on making error handling consistent in the get operation wrapper. NotFoundError is no longer preserved; all errors now follow a uniform wrapping strategy unless a custom onError handler is provided (commit 92cdb56).

Behavior Change

  • Remove NotFoundError passthrough in createGetWrapper: all errors are now wrapped with the generic "[operationName] Operation failed" error unless handled by onError (commit 92cdb56).
    • If you previously relied on catching NotFoundError directly from the get wrapper, update your logic to use a custom onError handler for special handling (commit 92cdb56).

Testing

  • Delete the unit test that verified NotFoundError passthrough behavior in createGetWrapper tests (commit 92cdb56).
  • Add NotFoundError import in createGetWrapper tests (commit 92cdb56).

Release

  • Finalize package version to 4.4.54 in package.json (commit 3e7d898).
Assets 2
Loading