Skip to content
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

[OGUI-1596] Update grpcErrorToNativeError to provide option for developer to use either message or details #2711

Merged

Conversation

graduta
Copy link
Member

@graduta graduta commented Jan 8, 2025

I DON'T have JIRA ticket

  • explain what this PR does
  • if it is new feature explain how plan to use it
  • test are added
  • documentation is changed or added
  • FLP integration tests were ran successful

PR which:

  • allows usage of either details or message for the custom error class
  • this is due to the fact that the message includes also the error key and code which is not needed as the custom error class already describes that but it might be useful to developers

Use details instead of message field of the gRPC error struct
@graduta graduta added the Backend label Jan 8, 2025
@graduta graduta requested a review from pepijndik January 8, 2025 09:59
@graduta graduta self-assigned this Jan 8, 2025
@graduta graduta changed the title [improv] Update grpcErrorToNativeError.js [OGUI-1596] Update grpcErrorToNativeError.js Jan 8, 2025
@graduta graduta requested a review from pepijndik January 8, 2025 13:01
@graduta graduta changed the title [OGUI-1596] Update grpcErrorToNativeError.js [OGUI-1596] Update grpcErrorToNativeError to provide option for developer to use either message or details Jan 8, 2025
pepijndik
pepijndik previously approved these changes Jan 8, 2025
@graduta graduta merged commit 11e0413 into dev Jan 8, 2025
15 checks passed
@graduta graduta deleted the improv/WEB/use-details-instead-of-message-in-grpc-error branch January 8, 2025 13:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

2 participants