-
-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
[BUG] [R] Code generated not immediately useable #6714
Comments
I've tested your spec with this PR: #5728, which provides better support for Enum in R. I was able to install it after purging some incorrect test files generated for Enum type:
Can you please also give it a try by building the JAR locally?
|
Thanks for the reply, and happy to try, but could you (if possible) provide a Docker-based setup? I have very little Java on my machine. What container with |
I leaned on a colleague and we got it sorted out. Thumbs up for the PR #5728. Resulting package now builds, lacks some documentation (normal at this stage) and fails some unit tests (ditto). I can live with that. So take this as my thumbs up for merging the PR! |
(For completeness I updated the initial post with the new URL of the YAML file describing our service; we have done some work at our end and that repo is now public.) |
There is one new bug. The generated code tries to deparse a |
Yes please open a new issue with the details for tracking |
Done, #6767. Thanks in advance for your consideration, it is appreciated! |
For the enum issue in auto-generated test files, I've filed #6936 to fix it. |
I am getting the same error as OP when I try to build my package: Steps to reproduce: git clone https://github.com/Scripta-Qumranica-Electronica/SQE_API_Connectors.git
cd SQE_API_Connectors/libs/r
R CMD build .
R CMD check qumranicaApiConnector_0.7.2.tar.gz Unfortunately I don't have enough experience with building R packages to debug much further than that, but perhaps there is some data type in my openapi spec that is giving some trouble. The r client code can be generated from the project root Thanks for any help you can provide, this is a really cool project. |
Hi @eddelbuettel, understand that this is more than 1y ago but this might be useful for you: for my case, the offending line was |
@chinsoon12 This is a by-now oldish bug report, and I don't think we have that issue anymore with the subsequent / current release. |
Tested the following with the R client generator in the latest master:
Both are building fine.
Please give the latest master another try and we're closing this for the time being. Please open a new issue for tracking if you need help. |
Thanks for the follow-up, and agreed that closing is fine. We continue to use the OpenAPI generator, and it works reliably (even if with small issues for which we post-process). |
@eddelbuettel can you please open an issue to the small issues so that we can later address those as well? Thanks. |
Absolutely. We are about to do some more work on the package generated by your tool (and some edits) off the yaml spec and I will aim to point some of the remaining things out. |
Bug Report Checklist
Description
Using the (Docker-based) openapi-generator-cli on a yaml template used otherwise, I end up with an R package that is not installable as a portion of the files are not parseable by R.
To reproduce:
which fails on
I am actually pretty experienced in R but find this hard to debug too. We can list the files that yield 'bad value' on sourcing though:
OpenAPI declaration file content or url
The YAML file is given above in the snippet and from here: https://github.com/TileDB-Inc/TileDB-Cloud-API-Spec/blob/master/openapi-v1.yaml
Command line used for generation
See above. I used your Docker container, downloaded yesterday
Steps to reproduce
See above, I followed your recommended invocation.
Related issues/PRs
N/A
Suggest a fix
N/A
The text was updated successfully, but these errors were encountered: