fix(grpc-error-status): decode google rpc status details - #11
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 73bc51edef
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d56dc7682a
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Таска
Как проверять
До фикса
Действие: импортировать публичную точку входа и декодировать grpc-status-details-bin с google.rpc.BadRequest
Ожидаемый результат: До фикса: импорт падает на exports сгенерированного proto, а декодированные details не содержат fieldViolationsList с field и description
После фикса
Действие: импортировать публичную точку входа и декодировать grpc-status-details-bin с google.rpc.BadRequest и full type URL
Ожидаемый результат: После фикса: публичная точка входа импортируется, ErrorStatus.fromServiceError и getErrorStatusDetails возвращают полный BadRequest detail
Пруфы