[R] fix error handling in the R client#22704
Merged
wing328 merged 2 commits intoOpenAPITools:masterfrom Jan 18, 2026
Merged
Conversation
mattpollock
commented
Jan 15, 2026
| {{/returnExceptionOnFailure}} | ||
| {{^returnExceptionOnFailure}} | ||
| if (is.null(local_var_resp$response) || local_var_resp$response == "") { | ||
| if (is.null(local_var_resp$response) || local_var_error_msg == "") { |
Contributor
Author
There was a problem hiding this comment.
local_var_resp$response can be a raw vector, meaning that the length(local_var_resp$response) is often greater than 1. This causes R errors because then local_var_resp$response == "" evaluates to a logical vector, but an if condition needs a logical scalar.
Contributor
Author
There was a problem hiding this comment.
based on AI feedback I updated this to || all(local_var_resp$response == "")
There was a problem hiding this comment.
4 issues found across 10 files
Prompt for AI agents (all issues)
Check if these issues are valid — if so, understand the root cause of each and fix them.
<file name="samples/client/echo_api/r/R/header_api.R">
<violation number="1" location="samples/client/echo_api/r/R/header_api.R:180">
P2: 5xx error handling can throw if response_as_text() returns NA (non-text body), because `local_var_error_msg == ""` yields NA and makes the `if` condition invalid.</violation>
</file>
<file name="samples/client/echo_api/r/R/body_api.R">
<violation number="1" location="samples/client/echo_api/r/R/body_api.R:261">
P2: 5xx error handling can throw when response_as_text returns NA; `local_var_error_msg == ""` yields NA and the `if` crashes for binary/invalid response bodies.</violation>
</file>
<file name="samples/client/echo_api/r/R/form_api.R">
<violation number="1" location="samples/client/echo_api/r/R/form_api.R:192">
P2: 5xx error handling can crash when response_as_text() yields character(0) or NA (empty/invalid body), because `local_var_error_msg == ""` makes the `if` condition throw instead of returning a fallback error response.</violation>
</file>
<file name="modules/openapi-generator/src/main/resources/r/api.mustache">
<violation number="1" location="modules/openapi-generator/src/main/resources/r/api.mustache:563">
P1: Primitive success path constructs ApiResponse with undefined variables (`content`, `resp`), causing runtime error and discarding the wrapper.</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
Member
|
r integration tests passed via #22722 |
Contributor
Author
|
thanks! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
@Ramanth, @saigiridhar21, @wing328
This PR ensures that a client API provides the status code when generating a new
ApiResponsefor errors. Previously this was not done, with the result that a confusing R error was thrown while trying to handle the REST error. This obfuscated the REST errors, making them difficult to diagnose.PR checklist
Commit all changed files.
This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
These must match the expectations made by your contribution.
You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example
./bin/generate-samples.sh bin/configs/java*.IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.
master(upcoming7.x.0minor release - breaking changes with fallbacks),8.0.x(breaking changes without fallbacks)"fixes #123"present in the PR description)Summary by cubic
Fixes R client error handling by always including the HTTP status code in ApiResponse and improving server error messages. This prevents secondary R errors and makes REST failures easier to debug.
Written for commit 0de41cf. Summary will update on new commits.