feat: handle database errors#11645
Open
aaqilniz wants to merge 1 commit into
Open
Conversation
aaqilniz
force-pushed
the
feat/handle-database-errors
branch
2 times, most recently
from
5240504 to
0a2b09c
Compare
aaqilniz
force-pushed
the
feat/handle-database-errors
branch
from
0a2b09c to
dc6c5f5
Compare
Signed-off-by: Muhammad Aaqil <aaqilcs102@gmail.com>
aaqilniz
force-pushed
the
feat/handle-database-errors
branch
from
dc6c5f5 to
b873faf
Compare
This file contains hidden or 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
1 participant
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.
The loopback app generally returns a 500 error code for most database-related errors. This PR adds a generic database error class and returns an appropriate error response by intercepting and modifying it at
legacy-datasource-juggler.Checklist
npm testpasses on your machinepackages/cliwere updatedexamples/*were updated👉 Check out how to submit a PR 👈