Issue 226 bookmark already exist error #276
Open
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
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.
Issue number: resolves #
Checklist
What is the current behavior?
For the backend, I use an already existing exception, BookmarkAlreadyExistsException, to handle cases where a bookmark already exists. This exception triggers a 409 Conflict HTTP response.
On the frontend, I catch the Conflict (409) error and use react-toastify to display a toast notification in the bottom-right corner of the screen, informing the user about the conflict that Bookmark already exist.
What is the new behavior?
Does this introduce a breaking change?
Other information