-
Notifications
You must be signed in to change notification settings - Fork 134
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
Handle exceptions from scotty as ScottyException #345
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a good change overall but I'd rather keep imports explicit and docstrings clearer.
f78880d
to
ed8f3d0
Compare
ed8f3d0
to
8f6162f
Compare
@ocramz Do you have any remaining concerns? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a good PR, but I still think captureParamMaybe
doesn't need the MonadIO constraint.
Also, shouldn't we add a deprecation warning to raiseStatus
?
8f6162f
to
6dd48a7
Compare
I'm going to deprecate |
@ocramz ping |
Hi @fumieval! I haven't forgotten about this, it's just that I'm on a
family holiday until the end of the month. Will look at it then! Best, Marco
…On Tue, 21 Nov 2023 at 15:49, Fumiaki Kinoshita ***@***.***> wrote:
@ocramz <https://github.com/ocramz> ping
—
Reply to this email directly, view it on GitHub
<#345 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABNBDKGHTZC6A7TS5WTF5CLYFRFGVAVCNFSM6AAAAAA6IR7HZ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRQGMZTENJWGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@ocramz I see, great! Have a wonderful vacation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great, thank you! 👍
@fumieval could you add a Changelog entry about this as well please? |
ff36c73
to
8107e16
Compare
@ocramz Sure, I updated the changelog |
This change replaces the use of
StatusError
byScottyException
. The idea is to avoid returning a error response in an arbitrary format and make it more reasonable to catch them, because catchingStatusError
doesn't make much senseFor the sake of compatibility, I kept the StatusError type but I think it should eventually be deprecated.
closes #338