Exposing helpful error messages #150
Merged
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
This was referenced Jan 6, 2019
Merged
blast-hardcheese
force-pushed
the
helpful-error-messages
branch
from
dd25dc8 to
a20ad9a
Compare
|
This flips the needle to overcommunicating client failures, which may be undesirable for consumers looking for security through obscurity. If this is your use case, using akka-http's |
blast-hardcheese
force-pushed
the
helpful-error-messages
branch
from
a20ad9a to
f8f2f39
Compare
Empty content results in NoContentException Parse Failure results in a parser exception
blast-hardcheese
force-pushed
the
helpful-error-messages
branch
from
f8f2f39 to
7f97cf3
Compare
|
@blast-hardcheese thanks a lot! |
|
@sledorze You're welcome! 0.41.4 is now available |
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.
scala.MatchError: foo (of class java.lang.String))NoContentExceptionInitial work towards #148, actually exposing validation errors in clients and servers. Customization will be more tricky, still need to think about how that will work.