Skip to content
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

distinct exception type thrown when best available objects not found #134

Conversation

bverbeken
Copy link
Member

Instead of throwing a generic SeatsioException (which is thrown in many cases, eg no focal point, event not found, etc), we now throw a BestAvailableObjectsNotFoundException (subclass of SeatsioException) to make it easier to handle this common specific case.

bverbeken and others added 5 commits December 23, 2024 21:08
…ny cases, eg no focal point, event not found, etc), we now throw a BestAvailableObjectsNotFoundException (subclass of SeatsioException) to make it easier to handle this common specific case.
Bumps the minor-and-patch-version-updates group with 1 update: [minitest](https://github.com/minitest/minitest).


Updates `minitest` from 5.25.2 to 5.25.4
- [Changelog](https://github.com/minitest/minitest/blob/master/History.rdoc)
- [Commits](minitest/minitest@v5.25.2...v5.25.4)

---
updated-dependencies:
- dependency-name: minitest
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch-version-updates
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…of first (trying to, and failing to) parse the response body
@bverbeken bverbeken requested a review from mroloux January 3, 2025 15:22
@bverbeken bverbeken merged commit 4eecf58 into master Jan 3, 2025
2 checks passed
@bverbeken bverbeken deleted the distinct-exception-type-thrown-when-best-available-objects-not-found branch January 3, 2025 15:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants