We no longer have error handling because of Sentry's flush, so having success and error states would be misleading. Likewise, none of the leftover code throw errors and there is no point in requiring callers to add do catch to use this code.
This is leftover work from #232. That PR has already been approved, so I created a new one to avoid noise.
[x] I have considered if this change warrants release notes and have added them to the appropriate section in the CHANGELOG.md if necessary.
We no longer have error handling because of Sentry's
flush, so havingsuccessanderrorstates would be misleading. Likewise, none of the leftover codethrowerrors and there is no point in requiring callers to adddo catchto use this code.This is leftover work from #232. That PR has already been approved, so I created a new one to avoid noise.
CHANGELOG.mdif necessary.