This repository has been archived by the owner on Aug 16, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 139
errors #93
Comments
rejoiner/rejoiner/src/test/java/com/google/api/graphql/rejoiner/RejoinerIntegrationTest.java Lines 56 to 78 in 96fbb95
rejoiner/rejoiner/src/test/java/com/google/api/graphql/rejoiner/RejoinerIntegrationTest.java Lines 137 to 141 in 96fbb95
|
Thank you, I think I know what to do. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Rejoiner's errors make me feel inconvenient because I can't define valid data to let the front desk staff know what the current error is, what kind of error is, because the current valid information is only message, which is not good judgment, I hope in When you execute responseObserver.onError(), you can have some properties in the error message, you can customize it, and let the background personnel return their own defined errors.
The text was updated successfully, but these errors were encountered: