distinct exception type thrown when best available objects not found #209
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ke it easier to handle this case
bverbeken
changed the title
schaloner
approved these changes
Dec 20, 2024
mroloux
approved these changes
Jan 3, 2025
bverbeken
deleted the
distinct-exception-type-for-best-available-not-found
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Instead of throwing a generic
SeatsioException(which is thrown in many cases, eg no focal point, event not found, etc), we now throw aBestAvailableObjectsNotFoundException(subclass ofSeatsioException) to make it easier to handle this common specific case.