-
Notifications
You must be signed in to change notification settings - Fork 594
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
Document that an exception thrown in a Path param unmarshaller is a rejection #18
Comments
Hey, I'd like to take this one, is anyone working on it already? |
No, seems no one has picked it up yet, thanks for looking into it! :) |
I agree, might be a good starting contribution! However, I find the ticket description a bit unclear. I think it's about using In that case, this code here seems to convert the exception into a rejection: https://github.com/akka/akka-http/blob/master/akka-http/src/main/scala/akka/http/scaladsl/server/directives/ParameterDirectives.scala#L115 It should probably be documented in the documentation of the |
Yes, it was about that; AFAIR someone expected "well it's an exception so should be an error page!", but indeed there we interpret it as "well, unable to extract, let's try another one", so as a rejection :) |
Good to see you here @ilke-zilci! |
Great! I will work on it then. It goes here, right? https://github.com/akka/akka-http/blob/master/docs/src/main/paradox/scala/http/routing-dsl/rejections.md |
As @jrudolph mentioned, I would document it next to the Path Parameter documentation pages (https://github.com/akka/akka-http/blob/master/docs/src/main/paradox/scala/http/routing-dsl/directives/parameter-directives/parameters.md) and then link to the rejection doc page as a "see for further info". And don't forget to document it for both Scala and Java docs :) |
Ok thanks. And sorry missed that line on the first read. |
Fixed in #1285. |
Issue by ktoso
Sunday Jul 10, 2016 at 14:01 GMT
Originally opened as akka/akka#20929
... and the next path will be attempted to be resolved.
This is different than exceptions inside of a route already (which would render as 500 usually then)
The text was updated successfully, but these errors were encountered: