DM-47796: Add Slack error reporting to fastapi_safir_app #289
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
Add support for Slack error reporting of uncaught exceptions to the `fastapi_safir_app` project template. We are currently adding this to all of our applications, so there's no reason for it to not be in the template, even though this may be eventually replaced with Sentry or some other exception reporting mechanism.
rra
force-pushed
the
tickets/DM-47796
branch
from
c9d38f0 to
23a7c25
Compare
Fix a few issues in the `fastapi_safir_app` template with UWS enabled that are autometically corrected by Ruff.
rra
force-pushed
the
tickets/DM-47796
branch
from
a445a13 to
5a627af
Compare
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.
Add support for Slack error reporting of uncaught exceptions to the
fastapi_safir_appproject template. We are currently adding this to all of our applications, so there's no reason for it to not be in the template, even though this may be eventually replaced with Sentry or some other exception reporting mechanism.