don't return dev messages in getUserMessage()
#1940
Closed
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.
Why?
Per guidance in V2 error guidelines, the
user_message
response field can be shown directly to users, but themessage
field is meant only for developers. The previous java implementation (#1911) conflated the two, which I worry may be confusing for users. I think the intended use case here is someting like:What?
null
fromgetUserMessage()
for v1 errorsSee Also
Changelog
stripeException.getUserMessage()
now returnsnull
for v1 errors instead of the developer-facing messagegetUserMessage()
, if non-null, can be passed directly to your users to explain what went wronggetUserMessage()
is null, then you should handle the error as usual, per the error handling docs.