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.
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.
I think we should make
ExceptionResponse
public but not its fields.We could change the fields to
pub(crate)
in order to still be able to access it in the crate.We should add at least add 2 methods for the
ExceptionResponse
:exception()
that returns theException
function_code()
that returns theFunctionCode
And we should also enable a simple creation of the
ExceptionResponse
with anew
method, or a method onRequest
/Response
maybe to create aExceptionResponse
from it.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.
After thinking about it more, I think only
Exception
should be in the public API.The user shouldn't have to know the existence of
ExceptionResponse
, the server should be able to build the appropriateResponse
type (eitherResponse
orExceptionResponse
) by the return of thecall
function.See #237 for more context.